mirror of
https://github.com/denoland/deno.git
synced 2025-09-22 02:12:33 +00:00
![]() Fixes https://github.com/denoland/deno/pull/28168#discussion_r1982740706 --------- Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com> |
||
---|---|---|
.. | ||
binary_package | ||
cached_only | ||
cached_only_after_first_run | ||
cjs_with_deps | ||
different_nested_dep | ||
dual_cjs_esm | ||
dynamic_import | ||
dynamic_import_json | ||
exec_file | ||
no_npm_after_first_run | ||
reload | ||
require_resolve_url | ||
run_existing_npm_package | ||
compile_npm_no_permissions.out | ||
deno_run_cjs.out | ||
deno_run_cowsay.out | ||
deno_run_cowthink.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
- Set the
DENO_TEST_UTIL_UPDATE_NPM=1
environment variable - Run the test and it should download the packages.
- If the package does not update, find it in
tests/registry/npm/
and download relatedregistry.json
file.
Using a custom npm package
- Add the custom package to
./registry/@denotest
- Reference
npm:@denotest/<your-package-name>
in the tests.