-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 runtime dependency "uuid" #9077
Conversation
@chradek, @jeremymeng: This dependency update is causing a build break in
The issue might be one of the known breaking changes: https://github.com/uuidjs/uuid/blob/master/CHANGELOG.md#-breaking-changes In general, we want to stay on the latest major of our depdendencies, but we could choose to stay on an older version of |
Ah, I've had to deal with this exact issue in another project. We should update our code to change how we import so we don't use the sub-module. |
Thanks. If you can make these changes with the existing version of |
I've updated the affected packages. |
a156887
to
87a61ca
Compare
/azp run js - core - ci |
Pull request contains merge conflicts. |
@chradek, @sadasant: The earlier fixes from @chradek unblocked the product build, but now test builds are failing in keyvault (two instances of this same error):
This might be the known breaking change "no more default export": https://github.com/uuidjs/uuid/blob/master/CHANGELOG.md#-breaking-changes |
I updated identity and a cosmos db sample. This time I did a more thorough search for all instances where Also ran rush build:test and see that keyvaults is building correctly now. |
/azp run js - eventhubs-client - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - eventhubs-processor - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
This reverts commit c866137.
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.
Just FYI, the latest versions of UUID don't work on Node < 14. Unfortunately, the latest version of Node anyone can run under Azure is 12.14. Accordingly, the new "exports" configuration in UUID 8.x's package.json results in errors starting our Node 12 Azure containers. You may either want to update your package.json's "engines" setting to reflect this new restriction, or consider downgrading the UUID version so it will work on older Node engines (like the latest version supported by Azure, Node v12.14). In the meantime, we've had to hardcode our package.json @azure/event-hubs to "5.1.0", since "^5.1.0" will pick up this patch version update. |
@dbarnespaychex: Thank you for reporting this. Can you please open an issue and include sample code and steps to reproduce the errors you are seeing? |
Issue #9515 opened. Thanks for your quick response. For anyone looking for a workaround, hard-code @azure/event-hubs to 5.1.0 in your package.json to get the older version of UUID. |
@dbarnespaychex: Thank you for the quick response as well. We are reviewing the issue right now and should have a reply by the end of the day. |
https://github.com/uuidjs/uuid/blob/master/CHANGELOG.md