Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: adding support for node 18, dropping node 12 #406

Merged
merged 6 commits into from
Apr 21, 2022

Conversation

erunion
Copy link
Member

@erunion erunion commented Apr 20, 2022

🧰 What's being changed?

Node 18 came out yesterday so I'm changing our engines list to support everything from Node 14 and on, dropping support for Node 12 in the process (which is being EOL'd in 10 days).

🧬 Testing

Tests on Node 18 should be passing.

@erunion erunion added the enhancement New feature or request label Apr 20, 2022
@domharrington
Copy link
Member

Looks like husky cannot be found on node 14 or 18:

image

I think we were reliant on buggy behaviour in npm@7 where `npm ci`
wasn't running some of the lifecycle hooks:
npm/cli#1905 (comment)

This got fixed in npm@8 but now our CI process breaks:
npm/cli@d825e90

Decided to follow the recommendations from husky's docs to do this so it
doesnt run the `prepare` step:

```sh
npm ci --ignore-scripts
```

https://github.com/typicode/husky/blob/0bcdac6b4dad6eedecc49cf3837ecc05b321db2e/docs/README.md#disable-husky-in-cidockerprod=
@domharrington domharrington merged commit 2d109b1 into main Apr 21, 2022
@domharrington domharrington deleted the feat/support-node18 branch April 21, 2022 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants