| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Construct a new module graph container for workers instead of sharing it
with the main worker.
Fixes #17248
Fixes #23461
---------
Co-authored-by: David Sherret <dsherret@gmail.com>
|
|
* https://github.com/denoland/deno_graph/pull/471
* https://github.com/denoland/deno_graph/pull/473
|
|
Closes https://github.com/denoland/deno/issues/23712
|
|
Closes https://github.com/denoland/deno/discussions/23814
|
|
Closes https://github.com/denoland/deno/issues/23796
|
|
Part of https://github.com/denoland/deno/issues/23624
|
|
of just publish (#23798)
Closes https://github.com/denoland/deno/issues/22835
|
|
|
|
`deno run script.ts <(some command)` is a valid use case -- let's allow
this to work without `--allow-all`.
Fixes #23703
|
|
Closes #23458
|
|
(#23730)
Closes https://github.com/denoland/deno/issues/23724
|
|
Fixes [23721](https://github.com/denoland/deno/issues/23721)
|
|
This PR implements the changes we plan to make to `deno install` in deno
2.0.
- `deno install` without arguments caches dependencies from
`package.json` / `deno.json` and sets up the `node_modules` folder
- `deno install <pkg>` adds the package to the config file (either
`package.json` or `deno.json`), i.e. it aliases `deno add`
- `deno add` can also add deps to `package.json` (this is gated behind
`DENO_FUTURE` due to uncertainty around handling projects with both
`deno.json` and `package.json`)
- `deno install -g <bin>` installs a package as a globally available
binary (the same as `deno install <bin>` in 1.0)
---------
Co-authored-by: Nathan Whitaker <nathan@deno.com>
|
|
Closes #23644
|
|
Moves the test npm registry server port from `4558` to `426x`
|
|
This is not a special path that can be used to escalate or bypass Deno
permissions, such as `--allow-env`.
|
|
`tests/registry` folder (#23717)
1. Moves the npm registries to their own dedicated ports.
2. Moves the data files out of `tests/testdata/npm/registry` to
`tests/registry/npm`.
|
|
Closes #23715
|
|
|
|
Allows writing named sub-tests. These are:
1. Filterable on the command line via `cargo test ...`
2. Run in parallel
3. Use a fresh temp and deno dir for each test (unlike steps)
|
|
|
|
This commit updates our testing npm registry to handle
additional `@denotest2` scope in addition to `@denotest`
scope. I might have to update it further in the future to handle
additional scopes, but it's good enough for now.
|
|
Closes https://github.com/denoland/deno/issues/23430
---------
Co-authored-by: Yoshiya Hinosawa <stibium121@gmail.com>
|
|
|
|
from paths not found (#23618)
Part of #22607 (probably closes it, but I haven't done thorough testing)
Makes it so that `require.resolve` with `paths` specified will fallback
to using the global cache when the paths can't be found when using a
global cache (not when using a node_modules folder)
|
|
|
|
Co-authored-by: David Sherret <dsherret@gmail.com>
|
|
Ref #17944, https://github.com/swc-project/swc/issues/8893
TypeScript removes the `assert` keywords in the transpile, so this PR
only works for JavaScript files
|
|
* https://github.com/denoland/deno_config/pull/51
Closes https://github.com/denoland/deno/issues/21440
|
|
Also did some renames from underscores to hyphens
|
|
|
|
|
|
Closes https://github.com/denoland/deno/issues/23564
|
|
When returning a jsr specifier for resolve it seems like deno core does
not work properly and hangs.
Closes https://github.com/denoland/deno/issues/23551
Closes https://github.com/denoland/deno/issues/23139
|
|
Closes https://github.com/denoland/deno_core/issues/648
Co-authored-by: Matt Mastracci <matthew@mastracci.com>
|
|
checking) (#23513)
Closes https://github.com/jsr-io/jsr/issues/322
|
|
By default, `deno serve` will assign port 8000 (like `Deno.serve`).
Users may choose a different port using `--port`.
`deno serve /tmp/file.ts`
`server.ts`:
```ts
export default {
fetch(req) {
return new Response("hello world!\n");
},
};
```
|
|
Files that were gitignored only were not included in the diagnostic.
|
|
Fixes #23456.
|
|
This commit changes the workspace support to provide all workspace
members to be available as imports based on their names and versions.
Closes https://github.com/denoland/deno/issues/23343
|
|
`Deno.ConnectTlsOptions.(certFile|certChain|privateKey)` (#23270)
Towards #23089
---------
Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com>
|
|
Towards #23089
---------
Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com>
|
|
npm binary commands like `vite` from a `node_modules/.bin` folder will
now execute when defined in a deno.json
Closes https://github.com/denoland/deno/issues/23477
|
|
This makes writing these tests a little easier.
|
|
|
|
|
|
Closes #23023
|
|
If a worker tried to flush large amounts of data right as the test was
ending, it could cause the flush sync marker to get lost.
|
|
css modules) (#23392)
This allows people to use imports like:
```ts
import "./app.css";
```
...with `deno check` in systems where there's a bundle step (ex. Vite).
This will still error when using it with `deno run` or if the referenced
file does not exist.
See test cases for behaviour.
|
