Skip to content

Files

Latest commit

 

History

History

npm

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
binary_package
binary_package
 
 
cached_only
cached_only
 
 
cached_only_after_first_run
cached_only_after_first_run
 
 
cjs_with_deps
cjs_with_deps
 
 
different_nested_dep
different_nested_dep
 
 
dual_cjs_esm
dual_cjs_esm
 
 
dynamic_import
dynamic_import
 
 
dynamic_import_json
dynamic_import_json
 
 
exec_file
exec_file
 
 
no_npm_after_first_run
no_npm_after_first_run
 
 
peer_deps_with_copied_folders
peer_deps_with_copied_folders
 
 
reload
reload
 
 
require_resolve_url
require_resolve_url
 
 
run_existing_npm_package
run_existing_npm_package
 
 
README.md
README.md
 
 
compile_npm_no_permissions.out
compile_npm_no_permissions.out
 
 
deno_run_cjs.out
deno_run_cjs.out
 
 
deno_run_cowsay.out
deno_run_cowsay.out
 
 
deno_run_cowthink.out
deno_run_cowthink.out
 
 
deno_run_esm.out
deno_run_esm.out
 
 

README.md

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.

Using a custom npm package

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