foster/deno
0
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2025-03-11 14:47:26 -04:00
Code Issues Packages 1 Wiki Activity
deno/cli/tests/testdata/npm
History
…
..
builtin_module_module
cached_only
cached_only_after_first_run
cjs_local_global_decls
cjs_reexport_collision
cjs_sub_path
cjs_this_in_exports
cjs_with_deps
compare_globals
conditional_exports
dual_cjs_esm
dynamic_import
env_var_re_export
esm
esm_import_cjs_default
import_map
no_npm_after_first_run
no_unstable fix(npm): always require --unstable flag even for esm (#15583) 2022-08-24 13:44:38 -04:00
nonexistent_file
registry
sub_paths
tarball_with_global_header
translate_cjs_to_esm
deno_run_cjs.out
deno_run_cowsay.out
deno_run_cowthink.out
deno_run_esm.out
deno_run_no_ext.out
deno_run_non_existent.out
README.md

README.md

npm test data

This folder contains test data for npm specifiers.

Registry

The registry is served by the test server (server in test_util) at http://localhost:4545/npm/registry/ 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.

Using a custom npm package

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