-
Notifications
You must be signed in to change notification settings - Fork 302
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
chore(deps): update dependency uuid to v9 #1518
Conversation
a6da9c9
to
a30843e
Compare
a30843e
to
06443dd
Compare
06443dd
to
9551912
Compare
1684409
to
3bf3640
Compare
3bf3640
to
20bdb19
Compare
f71c168
to
17ccf4e
Compare
17ccf4e
to
2bd8e29
Compare
@Thomaash Any reason not to merge this? see visjs/vis-data#990 (comment) |
117c0d8
to
dbda9d1
Compare
4a9ecda
to
7de693c
Compare
7de693c
to
bc01942
Compare
bc01942
to
41feacc
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.
On closer inspection we're not actually polyfilling IE11 anymore (the rule is > 0.1% and not dead
) so this can be merged.
🎉 This PR is included in version 7.7.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This PR contains the following updates:
7.0.3
->9.0.0
Release Notes
uuidjs/uuid
v9.0.0
Compare Source
⚠ BREAKING CHANGES
Drop Node.js 10.x support. This library always aims at supporting one EOLed LTS release which by this time now is 12.x which has reached EOL 30 Apr 2022.
Remove the minified UMD build from the package.
Minified code is hard to audit and since this is a widely used library it seems more appropriate nowadays to optimize for auditability than to ship a legacy module format that, at best, serves educational purposes nowadays.
For production browser use cases, users should be using a bundler. For educational purposes, today's online sandboxes like replit.com offer convenient ways to load npm modules, so the use case for UMD through repos like UNPKG or jsDelivr has largely vanished.
Drop IE 11 and Safari 10 support. Drop support for browsers that don't correctly implement const/let and default arguments, and no longer transpile the browser build to ES2015.
This also removes the fallback on msCrypto instead of the crypto API.
Browser tests are run in the first supported version of each supported browser and in the latest (as of this commit) version available on Browserstack.
Features
Bug Fixes
build
drop Node.js 8.x from babel transpile target (#603) (aa11485)
drop support for legacy browsers (IE11, Safari 10) (#604) (0f433e5)
drop node 10.x to upgrade dev dependencies (#653) (28a5712), closes #643
8.3.2 (2020-12-08)
Bug Fixes
8.3.1 (2020-10-04)
Bug Fixes
v8.3.2
Compare Source
v8.3.1
Compare Source
v8.3.0
Compare Source
Features
v8.2.0
Compare Source
Features
Bug Fixes
v8.1.0
Compare Source
Features
Bug Fixes
v8.0.0
Compare Source
⚠ BREAKING CHANGES
For native ECMAScript Module (ESM) usage in Node.js only named exports are exposed, there is no more default export.
Deep requiring specific algorithms of this library like
require('uuid/v4')
, which has been deprecated inuuid@7
, is no longer supported.Instead use the named exports that this module exports.
For ECMAScript Modules (ESM):
For CommonJS:
Features
Bug Fixes
7.0.3 (2020-03-31)
Bug Fixes
7.0.2 (2020-03-04)
Bug Fixes
7.0.1 (2020-02-25)
Bug Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.