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
[Release 3.0] - Update node to v18 #12663
Conversation
This commit also removes the fork of `pacote` that Meteor used to use - hopefully, the issues that were fixed with our patch are already fixed on upstream.
Bump the `source-map` version to fix the issue: mozilla/source-map#454. We are not updating the NPM version because there is an breaking change with the `npm config set python` which we use with `node-gyp`.
@matheusccastroo how can I run meteor from this fork? When I try standard way to described in docs and i do
|
# Conflicts: # meteor
@pociej You need to build the dev-bundle locally. You can do that by running |
// As per Npm 8, now the metadata is no longer inside .npm/package/node_modules/PACKAGE_NAME/package.json // now you have every metadata of every package inside .npm/package/node_modules/ at .npm/package/node_modules/.package-lock.json
…thers to start fresh for node 18
…ory command" This reverts commit 2e591f3.
…stalled correctly
cordova builds with server options
. It seems to be related to NPM.