-
Notifications
You must be signed in to change notification settings - Fork 22
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
[HOTFIX] Fix bad npm registry #294
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These files were deleted but don't we want to create new lock files?
🤦 |
84c59c2
to
daf10f4
Compare
daf10f4
to
710ee0a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That looks better :D One more question what about the command-expansion-server lock file? Was that one not messed up?
There was an issue in 0.53.1 and 0.54.0, so we'll lock it here for now
This has turned into a dependency nightmare. I think I've got it right this time. |
Great question. I have no idea. It's clearly right here https://github.com/NASA-AMMOS/aerie/blob/hotfix/bad-npm-source/command-expansion-server/package-lock.json#L1046 Perhaps I had already installed the 0.3.1 locally on a different day when my registry was correctly set and so the package-lock didn't change. |
@goetzrrGit finally got it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥵
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merge, Merge, Merge
Description
When I updated the user code runner, my npm registry was set to JPL artifactory, so that got encoded into the package-lock files. This fixes that blunder.
Also locks version for typescript-json-schema to work around a dependency error with the 0.53.1 version
Verification
Documentation
Future work