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

Explicitly declare Node version support: 10, 12, 14+. #582

Merged
merged 2 commits into from
Oct 21, 2020

Conversation

rwjblue
Copy link
Collaborator

@rwjblue rwjblue commented Oct 21, 2020

Updates each of our published packages' package.json files to have the following engines field value:

{
  "engines": {
    "node": "10.* || 12.* || >= 14"
  }
}

This is the list of currently supported Node releases (based on nodejs.org's release page).

We may want to consider this a breaking change (due to the @embroider/router package having had engines defined that allowed Node 8), but for most of the packages there simply was no declaration of support at all which IMHO means adding engines is "safe".

Updates each of our published packages' `package.json` files to have the
following engines field value:

```json
{
  "engines": {
    "node": "10.* || 12.* || >= 14"
  }
}
```

This is the list of currently supported Node releases (based on
nodejs.org).

We _may_ want to consider this a breaking change (due to the
`@embroider/router` package having had engines defined that allowed Node
8), but for most of the packages there simply was no declaration of
support at all which IMHO means adding `engines` is "safe".
"node": "8.* || >= 10.*"
"node": "10.* || 12.* || >= 14"
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change should probably be considered "breaking".

@rwjblue rwjblue changed the title Add (or update) engines to indicate Node support. Explicitly declare Node version support: 10, 12, 14+. Oct 21, 2020
@rwjblue rwjblue mentioned this pull request Oct 21, 2020
@ef4
Copy link
Contributor

ef4 commented Oct 21, 2020

(I merged master in because I want to see that my recent test suite changes are working well in a PR like this.)

@ef4 ef4 merged commit f090260 into embroider-build:master Oct 21, 2020
@rwjblue rwjblue deleted the explicit-engines branch October 21, 2020 19:23
simonihmig added a commit that referenced this pull request Jun 8, 2023
This will make `macroCondition()` do full branch elimination even in development, as long as no macro is involved that has a runtime implementation (`get*Config()`, `isTesting` have).

Closes #582
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants