Upgrade dependencies #160
Open
Upgrade dependencies #160
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The previous version of Meteor (1.8.0.1) cannot even download its core packages anymore (`error: certificate has expired`) - Change `.meteor/release` to (second-to-)latest version du jour - Run `meteor npm i`, which (despite failing ultimately) updates all `"integrity"` records in `package.json` to a modern `sha512-` fingerprint, by virtue of the previous step having upgraded the underlying `npm` command
``` meteor npm i --save-dev @angular/compiler-cli@=7.2.15 meteor npm i --save @babel/runtime@=7.21.5 ``` (Also, edit `package.json` to pinpoint dependencies to a precise version — Something I can't seem to do using the `meteor npm` command line.) Required because - `@angular/[email protected]` used to depend on `chokidar@^1.4.2`, which depended on `fsevents@^1.0.0`, which we cannot build (because v8 API something something) nor download in binary form anymore (because it got withdrawn from the server it was at), - `@babel/[email protected]` spewed `Error: Cannot find module '/Users/quatrava/Dev/angular-meteor/angular-meteor-base/.meteor/local/build/programs/server/node_modules/@babel/runtime/helpers/objectSpread2'` in a manner very similar to [this previous problem](https://forums.meteor.com/t/solved-cannot-find-module-babel-runtime-helpers-builtin-objectspread-after-update-meteor-to-1-6-1-1/43034/2) which was also cured by upgrading it. Now both `meteor npm i` completes successfully (albeit with `npm audit` issues, some of them critical).
Done by editing `.meteor/versions` by hand, as `meteor upgrade` can't (it chokes on trying to build `node-sass`, which is no longer downloadable). Now both `meteor npm i` and `meteor` complete successfully.
Now that Meteor starts up successfully, it wants to make these changes to its package lineup.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
💡 Every single change in this PR was carefully confirmed to be indispensable (as of today) to get the demo app to start up again.