| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-01-24 | feat: Expand 'imports' section of deno.json (#22087) | Bartek Iwańczuk | |
| This commit adds automatic expansion of "imports" field in "deno.json" file. If "npm:" or "jsr:" imports are encountered we automatically try to add a "directory" remapping. Previously users had to specify entries for both `foo` and `foo/` to be able to import like `import { symbol1 } from "foo";` and `import { symbol2 } from "foo/some_file.js"`: ``` { "imports": { "foo": "npm:@foo/bar", "foo/": "npm:/@foo/bar/", } ``` With this change users can only add entry for `foo`: ``` { "imports": { "foo": "npm:@foo/bar", } ``` The entry for `foo/` will be provided automatically. Similarly if user provides "directory" remapping explicitly, we will not overwrite it. | |||
| 2023-05-10 | feat(compile): unstable npm and node specifier support (#19005) | David Sherret | |
| This is the initial support for npm and node specifiers in `deno compile`. The npm packages are included in the binary and read from it via a virtual file system. This also supports the `--node-modules-dir` flag, dependencies specified in a package.json, and npm binary commands (ex. `deno compile --unstable npm:cowsay`) Closes #16632 | |||
| 2023-02-23 | feat(npm): support bare specifiers from package.json in more subcommands and ↵ | David Sherret | |
| language server (#17891) | |||
