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

Strictly enforce the node version required #101

Merged
merged 1 commit into from
Dec 29, 2023

Conversation

andrewhood125
Copy link
Contributor

This is helpful to avoid node versions that will fail. With loud npm install output, warnings can go unseen. With this change because of the engine requirements specified upstream by the minecraft-protocol package if someone attempts to npm install with an unsupported version of node the process will abort with an error.

Screenshot 2023-08-19 at 5 41 29 PM

This is helpful to avoid versions that will fail and with loud npm
install output, warnings can go unseen. With this change because of the
engine requirements specified upstream by the minecraft-protocol package
if someone attempts to npm install with an unsupported version of node
the process will abort with an error.
@Heath123 Heath123 merged commit 6c656d0 into Heath123:master Dec 29, 2023
@Heath123
Copy link
Owner

Wait, but this also blocks newer Node versions that seem like they should work fine?

@andrewhood125
Copy link
Contributor Author

@Heath123 it works similar to how versions are set in the package.json. You can give a range >=16, a list 16 || 18 etc.

I just checked out the main branch and it looks like the version of @azure/msal-node specifies a engine requirement here:

https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/011c397e3e815709e9b108eed660b993239f9a49/lib/msal-node/package.json#L66

That is what is currently stopping node v20 for being valid for example. The latest version of that package does not have that engine requirement. I'm not sure what all upgrading packages would entail but that should solve the issue of not being able to run the latest node versions.

andrewhood125 added a commit to andrewhood125/pakkit that referenced this pull request Jan 3, 2024
Background information [here].

[here](Heath123#101)
andrewhood125 added a commit to andrewhood125/pakkit that referenced this pull request Jan 3, 2024
Background information [here].

[here]: Heath123#101
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