foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-01 16:51:13 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/tests/specs/publish/invalid_import/invalid_import.out

32 lines
1.3 KiB
Text
Raw Normal View History

feat: add `--allow-import` flag (#25469) This replaces `--allow-net` for import permissions and makes the security sandbox stricter by also checking permissions for statically analyzable imports. By default, this has a value of `--allow-import=deno.land:443,jsr.io:443,esm.sh:443,raw.githubusercontent.com:443,gist.githubusercontent.com:443`, but that can be overridden by providing a different set of hosts. Additionally, when no value is provided, import permissions are inferred from the CLI arguments so the following works because `fresh.deno.dev:443` will be added to the list of allowed imports: ```ts deno run -A -r https://fresh.deno.dev ``` --------- Co-authored-by: David Sherret <dsherret@gmail.com>
2024-09-25 21:50:54 -04:00
[# notice that the remote module is not downloaded here. This is so we do not need to add an --allow-import permission here]
chore: fix flaky net_listen_allow_localhost_4555 (#23726) Moves the test npm registry server port from `4558` to `426x`
2024-05-07 13:21:56 -04:00
Download http://localhost:4260/chalk
Download http://localhost:4260/chalk/chalk-5.0.1.tgz
feat(unstable/lint): no-slow-types for JSR packages (#22430) 1. Renames zap/fast-check to instead be a `no-slow-types` lint rule. 1. This lint rule is automatically run when doing `deno lint` for packages (deno.json files with a name, version, and exports field) 1. This lint rules still occurs on publish. It can be skipped by running with `--no-slow-types`
2024-02-19 10:28:41 -05:00
Checking for slow types in the public API...
feat(publish): error on invalid external imports (#22088)
2024-01-24 16:59:18 -05:00
error[invalid-external-import]: invalid import to a non-JSR 'http' specifier
--> [WILDCARD]mod.ts:1:8
|
1 | import "http://localhost:4545/welcome.ts";
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the specifier
fix: better handling of npm resolution occurring on workers (#24094) Closes https://github.com/denoland/deno/issues/24063
2024-06-05 11:04:16 -04:00
|
feat(publish): error on invalid external imports (#22088)
2024-01-24 16:59:18 -05:00
= hint: replace this import with one from jsr or npm, or vendor the dependency into your package
info: the import was resolved to 'http://localhost:4545/welcome.ts'
info: this specifier is not allowed to be imported on jsr
info: jsr only supports importing `jsr:`, `npm:`, and `data:` specifiers
docs: https://jsr.io/go/invalid-external-import
error[invalid-external-import]: invalid import to a non-JSR 'http' specifier
--> [WILDCARD]mod.ts:2:8
|
2 | import "$echo";
| ^^^^^^^ the specifier
fix: better handling of npm resolution occurring on workers (#24094) Closes https://github.com/denoland/deno/issues/24063
2024-06-05 11:04:16 -04:00
|
feat(publish): error on invalid external imports (#22088)
2024-01-24 16:59:18 -05:00
= hint: replace this import with one from jsr or npm, or vendor the dependency into your package
info: the import was resolved to 'http://localhost:4545/echo.ts'
info: this specifier is not allowed to be imported on jsr
info: jsr only supports importing `jsr:`, `npm:`, and `data:` specifiers
docs: https://jsr.io/go/invalid-external-import
error: Found 2 problems
Copy permalink