-
Notifications
You must be signed in to change notification settings - Fork 100
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
Update TypeSpec npm packages in dev container #7812
Comments
👋 @brooke-hamilton Thanks for filing this issue. A project maintainer will review this issue and get back to you soon. We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue. For more information on our triage process please visit our triage overview |
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up. We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue. For more information on our triage process please visit our triage overview |
@ytimocin @brooke-hamilton do we know why this isn't covered by depdendabot already? |
I will check this. Another update: when we run |
Unassigned myself from this issue for now. |
Completed |
Area for Improvement
The
postCreateCommand
in the dev container runsnpm ci
in thetypespec
folder. Some of the packages specified in thepackage-lock.json
file are out of date.Observed behavior
Building and running the dev container shows that some of the packages need to be updated.
Desired behavior
Packages should be current.
Proposed Fix
npm update
in thetypespec
folder and submit a PR for the changes.rad Version
0.36
Operating system
No response
Additional context
No response
Would you like to support us?
AB#12985
The text was updated successfully, but these errors were encountered: