deno/tests/testdata/npm
2025-05-08 17:44:22 +00:00
..
binary_package
cached_only refactor: remove CliNpmRegistryApi (#27222) 2024-12-03 19:44:56 -05:00
cached_only_after_first_run
cjs_with_deps fix(info): move "version" field to top of json output (#25890) 2024-09-26 15:57:12 -04:00
different_nested_dep
dual_cjs_esm
dynamic_import chore: fix flaky net_listen_allow_localhost_4555 (#23726) 2024-05-07 17:21:56 +00:00
dynamic_import_json
exec_file fix(ext/node): improve shelljs compat with managed npm execution (#24912) 2024-08-16 12:48:48 +09:00
no_npm_after_first_run
reload
require_resolve_url
run_existing_npm_package fix(npm): ensure scoped package name is encoded in URLs (#26390) 2024-10-18 20:38:57 +02:00
compile_npm_no_permissions.out feat: Deno.cwd() no longer requires --allow-read permission (#27192) 2025-01-27 15:13:59 +01:00
deno_run_cjs.out
deno_run_cowsay.out
deno_run_cowthink.out
deno_run_esm.out
README.md fix: bump default @types/node version range to 22.15.14 (#28407) 2025-05-08 17:44:22 +00:00

npm test data

This folder contains test data for npm specifiers.

Registry

The registry is served by the test server (server in tests/util/server) at http://localhost:4260/ via the ./registry folder.

Updating with real npm packages

  1. Set the DENO_TEST_UTIL_UPDATE_NPM=1 environment variable
  2. Run the test and it should download the packages.
  3. If the package does not update, find it in tests/registry/npm/ and download related registry.json file.

Using a custom npm package

  1. Add the custom package to ./registry/@denotest
  2. Reference npm:@denotest/<your-package-name> in the tests.