-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Dependency package esbuild has a new version available #29683
Labels
Comments
3 tasks
mpodwysocki
added a commit
that referenced
this issue
May 21, 2024
### Packages impacted by this PR - @azure/core-amqp ### Issues associated with this PR - #29683 ### Describe the problem that is addressed by this PR Removes esbuild and its polyfills for Node in favor of vite and vite node plugins. ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? ### Are there test cases added in this PR? _(If not, why?)_ ### Provide a list of related PRs _(if any)_ ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ### Checklists - [ ] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [ ] Added a changelog (if necessary)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have identified a dependency on version 0.20.2 of esbuild. A new version (0.21.3) is available for upgrade.
Following are the steps to upgrade package dependency.
Understand the breaking changes between the version being used and the version you want to upgrade to.
Identify all packages that take a dependency on this package.
Go to the root folder for each such package (/sdk/service-name/package-name) and update package.json to have the new version.
Run rush update to ensure the new version is pulled in.
Make relevant changes to absorb the breaking changes.
Repeat steps 3 to 5 for each of the packages that have a dependency on this package.
The text was updated successfully, but these errors were encountered: