{"bugs":{"url":"https://github.com/node-opcua/node-opcua-crypto/issues"},"dist":{"shasum":"5cd8cd0b56d5295be5d98e86dcbbe74c3a34f111","tarball":"https://registry.npmjs.org/node-opcua-crypto/-/node-opcua-crypto-6.2.0.tgz","fileCount":158,"integrity":"sha512-EX24n3hcvit2RP0C/AUeA3lcWFSkWv49fgKOZ7FflyyJ77w7tcrjr5CUV0ulE4XB0Ca2rP1cvSUlLqb95IQScg==","signatures":[{"sig":"MEYCIQDos3n/cM7kB3CY2/ndYOERHwv/+n/ab53w94qVV2ldFgIhALucx5PJ3fHPQtSCw9AFB9GctN9JiNPafhHG2YtF9iaN","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDBjXMZeDhVj7VMTKrvAq6MyfJ4eTzXwnRtwFmcYPfyNAIhAIAp9x33bVxNr6UPiaB6qEUUrYhsFmmMBa4sygsSwaJa","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/node-opcua-crypto@6.2.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":577996},"main":"./dist/index.js","name":"node-opcua-crypto","type":"module","types":"./dist/index.d.ts","//main":"main/types are the pre-'exports' fallback, used only by resolvers that ignore the exports map (TypeScript's classic 'node' resolution, older bundlers). They are deliberately left as the ESM pair so that path behaves exactly as it did before - do not 'fix' one without the other, or that fallback becomes a CJS file described by ESM types.","author":{"name":"Etienne Rossignon"},"engine":{"node":">=18.0"},"//build":"Built with `tsc -b` (unbundled, per-file emit, module/moduleResolution NodeNext), mirroring the node-opcua monorepo scheme. dist/ therefore holds one .js + .d.ts per source file: dist/index.js, dist/source/*.js (incl. index_web.js) and dist/source_nodejs/*.js - exactly the paths the exports map and main/types reference. The source already carries explicit .js extensions on every relative import, which NodeNext requires.","exports":{".":{"import":{"types":"./dist/index.d.ts","default":"./dist/index.js"},"browser":{"types":"./browser/index.d.ts","default":"./browser/index.js"},"default":{"types":"./dist/index.d.ts","default":"./dist/index.js"}},"./web":{"import":{"types":"./dist/source/index_web.d.ts","default":"./dist/source/index_web.js"},"default":{"types":"./dist/source/index_web.d.ts","default":"./dist/source/index_web.js"}},"./node":{"import":{"types":"./dist/source_nodejs/index.d.ts","default":"./dist/source_nodejs/index.js"},"default":{"types":"./dist/source_nodejs/index.d.ts","default":"./dist/source_nodejs/index.js"}},"./package.json":"./package.json"},"gitHead":"ba3f9e5151ed01aab242b2807556a49692bc59db","license":"MIT","makedoc":"npx typedoc packages/node-opcua-crypto/index.ts -out doc","scripts":{"lint":"biome check","build":"tsc -b","format":"biome format --write","makedoc":"npx typedoc  index.ts --excludeNotDocumented --exclude \"_*\" --excludePrivate --excludeProtected --excludeExternals -out doc","prepare":"npm run build","lint:fix":"biome lint --fix","build:demo":"node web/esbuild.mjs","experiment":"tsc test/test_peculiar_edge_case.ts -t es2021 -m nodenext","build:clean":"npx rimraf ./dist ./dist-* *.tsbuildinfo","cost-of-modules":"npx -y slow-deps"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"bbefd92e-0d8b-4f0d-8265-75e060ead8d2"}},"homepage":"https://github.com/node-opcua/node-opcua-crypto#readme","keywords":["OPCUA","opcua","m2m","iot","opc ua","internet of things"],"//esm-only":"This package is ESM-only: tsc emits ESM only (no dist/*.cjs, no dist/*.d.cts). Each subpath's \"default\" condition points at the same ESM as \"import\", so require() RESOLVES too: on Node 22.12+ it loads the ES module (require(esm); the built graph has no top-level await), on older Node it fails with ERR_REQUIRE_ESM rather than the previous ERR_PACKAGE_PATH_NOT_EXPORTED (which the import-only map produced on ALL versions). A CommonJS consumer may still use dynamic import() everywhere. The ESM smoke test lives in packages/node-opcua-crypto-test/test-esm.","repository":{"url":"git://github.com/node-opcua/node-opcua-crypto.git","type":"git"},"_npmVersion":"lerna/10.0.1/node@v24.21.0+x64 (linux)","description":"Crypto tools for Node-OPCUA","directories":{},"maintainers":[{"name":"erossignon","email":"etienne.rossignon@sterfive.com"}],"_nodeVersion":"24.21.0","dependencies":{"sshpk":"^1.18.0","@peculiar/x509":"^2.1.0","reflect-metadata":"^0.2.2","@peculiar/asn1-cms":"^2.10.0","@peculiar/asn1-pfx":"^2.10.0","@peculiar/asn1-rsa":"^2.10.0","@peculiar/asn1-x509":"^2.10.0","@peculiar/webcrypto":"^1.7.1","@peculiar/asn1-pkcs8":"^2.10.0","@peculiar/asn1-pkcs9":"^2.10.0","@peculiar/asn1-schema":"^2.10.0"},"//exports-web":"./web is the browser-safe entry (dist/source/index_web.js). It imports assert/constants/crypto/path/url, so the consumer's bundler must supply those. Anyone wanting a zero-config, fully pre-bundled browser build installs the separate node-opcua-crypto-web package instead - inlining it here would add ~344 KB gzip to every Node install for something Node consumers never import. NOTE: keep notes like this OUTSIDE the exports object - every key in there is a subpath pattern, and a non-'.' key alongside '.' keys invalidates the whole map.","_hasShrinkwrap":false,"devDependencies":{"util":"^0.12.5","assert":"^2.1.0","buffer":"^6.0.3","events":"^3.3.0","@types/node":"^24.19.1","@types/sshpk":"^1.17.5","vm-browserify":"^1.1.2","string_decoder":"^1.3.0","crypto-browserify":"^3.12.1","stream-browserify":"^3.0.0","constants-browserify":"^1.0.0"},"peerDependencies":{"node-opcua-crypto-web":"^6.0.0"},"//exports-browser":"the \"browser\" condition MUST stay first - conditions are matched in declaration order, and import would otherwise win and hand a browser bundler the Node build. It resolves to a ~60 byte stub that re-exports the optional node-opcua-crypto-web peer, so Node consumers pay nothing for it. If a browser consumer has not installed that peer, their bundler fails at build time with an unresolved 'node-opcua-crypto-web' - that is the intended signal; ./web remains available as the bring-your-own-polyfills path that needs no peer.","//peerDependencies":"optional on purpose: only browser consumers resolving the \"browser\" condition need it, and npm must not pull it into a Node install. See browser/index.js. NOTE: `lerna version` rewrites sibling ranges in dependencies/devDependencies but NOT in peerDependencies - bump this by hand at each release. A stale caret range still resolves, so nothing breaks loudly; it just drifts.","peerDependenciesMeta":{"node-opcua-crypto-web":{"optional":true}},"_npmOperationalInternal":{"tmp":"tmp/node-opcua-crypto_6.2.0_1791455283530_0.03257330771115474","host":"s3://npm-registry-packages-npm-production"},"_id":"node-opcua-crypto@6.2.0","version":"6.2.0"}