Innovenergy
/
Innovenergy_trunk
2
1
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
Innovenergy_trunk/frontend/node_modules/uuid/CHANGELOG.md

16 KiB
Raw Blame History

Changelog

All notable changes to this project will be documented in this file. See standard-version for commit guidelines.

9.0.0 (2022-09-05)

⚠ 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

8.3.0 (2020-07-27)

Features

8.2.0 (2020-06-23)

Features

Bug Fixes

  • prepare package exports for webpack 5 (#468) (8d6e6a5)

8.1.0 (2020-05-20)

Features

  • improve v4 performance by reusing random number array (#435) (bf4af0d)
  • optimize V8 performance of bytesToUuid (#434) (e156415)

Bug Fixes

8.0.0 (2020-04-29)

⚠ BREAKING CHANGES

  • For native ECMAScript Module (ESM) usage in Node.js only named exports are exposed, there is no more default export.

    -import uuid from 'uuid';
-console.log(uuid.v4()); // -> 'cd6c3b08-0adc-4f4b-a6ef-36087a1c9869'
+import { v4 as uuidv4 } from 'uuid';
+uuidv4(); // ⇨ '9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d'

  • Deep requiring specific algorithms of this library like require('uuid/v4'), which has been deprecated in uuid@7, is no longer supported.

    Instead use the named exports that this module exports.

    For ECMAScript Modules (ESM):

    -import uuidv4 from 'uuid/v4';
+import { v4 as uuidv4 } from 'uuid';
uuidv4();

    For CommonJS:

    -const uuidv4 = require('uuid/v4');
+const { v4: uuidv4 } = require('uuid');
uuidv4();

Features

Bug Fixes

  • add CommonJS syntax example to README quickstart section (#417) (e0ec840)

7.0.3 (2020-03-31)

Bug Fixes

  • make deep require deprecation warning work in browsers (#409) (4b71107), closes #408

7.0.2 (2020-03-04)

Bug Fixes

7.0.1 (2020-02-25)

Bug Fixes

  • clean up esm builds for node and browser (#383) (59e6a49)
  • provide browser versions independent from module system (#380) (4344a22), closes #378

7.0.0 (2020-02-24)

⚠ BREAKING CHANGES

  • The default export, which used to be the v4() method but which was already discouraged in v3.x of this library, has been removed.
  • Explicitly note that deep imports of the different uuid version functions are deprecated and no longer encouraged and that ECMAScript module named imports should be used instead. Emit a deprecation warning for people who deep-require the different algorithm variants.
  • Remove builtin support for insecure random number generators in the browser. Users who want that will have to supply their own random number generator function.
  • Remove support for generating v3 and v5 UUIDs in Node.js<4.x
  • Convert code base to ECMAScript Modules (ESM) and release CommonJS build for node and ESM build for browser bundlers.

Features

  • add UMD build to npm package (#357) (4e75adf), closes #345
  • add various es module and CommonJS examples (b238510)
  • ensure that docs are up-to-date in CI (ee5e77d)
  • hybrid CommonJS & ECMAScript modules build (a3f078f)
  • remove insecure fallback random number generator (3a5842b), closes #173
  • remove support for pre Node.js v4 Buffer API (#356) (b59b5c5)
  • rename repository to github:uuidjs/uuid (#351) (c37a518), closes #338

Bug Fixes

  • add deep-require proxies for local testing and adjust tests (#365) (7fedc79)
  • add note about removal of default export (#372) (12749b7), closes #370
  • deprecated deep requiring of the different algorithm versions (#361) (c0bdf15)

3.4.0 (2020-01-16)

Features

3.3.3 (2019-08-19)

Bug Fixes

  • no longer run ci tests on node v4
  • upgrade dependencies

3.3.2 (2018-06-28)

Bug Fixes

3.3.1 (2018-06-28)

Bug Fixes

  • fix #284 by setting function name in try-catch (f2a60f2)

3.3.0 (2018-06-22)

Bug Fixes

Features

  • enforce Conventional Commit style commit messages (#282) (cc9a182)

3.2.1 (2018-01-16)

Bug Fixes

3.2.0 (2018-01-16)

Bug Fixes

  • remove mistakenly added typescript dependency, rollback version (standard-version will auto-increment) (09fa824)
  • use msCrypto if available. Fixes #241 (#247) (1fef18b)

Features

3.1.0 (2017-06-17)

Bug Fixes

  • (fix) Add .npmignore file to exclude test/ and other non-essential files from packing. (#183)
  • Fix typo (#178)
  • Simple typo fix (#165)

Features

  • v5 support in CLI (#197)
  • V5 support (#188)

3.0.1 (2016-11-28)

  • split uuid versions into separate files

3.0.0 (2016-11-17)

  • remove .parse and .unparse

2.0.0

  • Removed uuid.BufferClass

1.4.0

  • Improved module context detection
  • Removed public RNG functions

1.3.2

  • Improve tests and handling of v1() options (Issue #24)
  • Expose RNG option to allow for perf testing with different generators

1.3.0

  • Support for version 1 ids, thanks to @ctavan!
  • Support for node.js crypto API
  • De-emphasizing performance in favor of a) cryptographic quality PRNGs where available and b) more manageable code