NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #4702 most downloaded on npm
A tiny (230B) and fast UUID (v4) generator for Node and the browser
Last release 4 years ago
no release in 18 months
Ships fairly regularly
a new release about every 1.5 years
Some releases are documented
notes for 2 of 4 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
4 releases · first in 2020
One column per quarter.
Add "types" conditions to exports map (#10): 4f36a44
exports map (#10): 4f36a44Full Changelog: https://github.com/lukeed/uuid/compare/v2.0.0...v2.0.1
Replaced default export with a named v4 export: 3e77ae9 `diff -- import uuid from '@lukeed/uuid'; ++ import { v4 as uuid } from '@lukeed/uuid'; `
Replaced default export with a named v4 export: 3e77ae9
-- import uuid from '@lukeed/uuid';
++ import { v4 as uuid } from '@lukeed/uuid';
Module now ships "non-secure" implementation (via Math.random) by default: 603674b, 4da1a49
The cryptographically secure (CSPRNG) implementation is now exported separately as @lukeed/uuid/secure.
-- import uuid from '@lukeed/uuid';
++ import { v4 as uuid } from '@lukeed/uuid/secure';
Removed "browser" entry from package.json config: e77255c
_While @lukeed/uuid/secure still uses the environment's crypto module, aliasing crypto has been moved to a separate @lukeed/csprng module. Bundlers and/or Node.js ESM will still follow the path resolution(s).
Module now includes separate "secure" vs "non-secure" modes: 603674b, 4da1a4, 4da1a49 This allows you to choose an implementation based on your needs~! AKA – you can trade speed for security if/when desired.
Added exports map for native Node.js ESM support: b3f97bb
@lukeed/uuid/secure usage example: 53bcd1bdevDependency versions: 60363c1Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →