| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-08-31 | chore: remove DENO_FUTURE=1 from spec tests (#25329) | Bartek Iwańczuk | |
| Towards https://github.com/denoland/deno/issues/25241 | |||
| 2024-07-19 | fix(cli): Respect implied BYONM from DENO_FUTURE in `deno task` (#24652) | Nathan Whitaker | |
| Regression from https://github.com/denoland/deno/commit/04f9db5b2217fe06f88e76146aac6362ff0b0b86 Originally I thought to fix the issue in the PR we needed to explicitly pass through the `node-modules-dir` flag, but after applying the correct fix that david pointed out (setting `NPM_PROCESS_STATE`) that wasn't necessary (or correct). We had a test for deno task with BYONM, but it only tested with `"unstable": ["byonm"]` in deno.json, so it didn't catch this. | |||
| 2024-04-20 | feat(task): support running npm binary commands in deno.json (#23478) | David Sherret | |
| 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 | |||
 |
index : deno.git | |
| Unnamed repository; edit this file 'description' to name the repository. | User & |
| summaryrefslogtreecommitdiff |