Project Fails to build without npm:@types/babel__core

[lishaduck]

Unless I install npm:@types/babel__core manually, type checking the default starter app (with lockfile nuked & all that) errors with:

error: Failed resolving types. [ERR_TYPES_NOT_FOUND] Could not find types for 'file:///Users/dukese01/Developer/webmaster-25-26/node_modules/.deno/@[email protected]/node_modules/@babel/core/index.js' imported from 'https://jsr.io/@fresh/plugin-vite/1.0.7/src/plugins/deno.ts'
    at https://jsr.io/@fresh/plugin-vite/1.0.7/src/plugins/deno.ts:10:24

It seems like probably a JSR bug? Might need to added to "types": [] too...

---

Also, could we pretty please get an esbuild bump? It pulls in two versions when I nuke the lockfile, and b/c Deno doesn't have dedupe functionality, I've got to resort to manually editing the lockfile, which sucks.

---

Associated Deno issue: https://github.com/denoland/deno/issues/31352

[cailloumajor]

I have a similar issue.

With "nodeModulesDir": "manual" in deno.json, deno task check fails with the following message:

Task check deno fmt --check . && deno lint . && deno check **/*.ts && deno check **/*.tsx
Checked 32 files
Checked 26 files
error: Failed resolving types. [ERR_TYPES_NOT_FOUND] Could not find types for 'file:///workspaces/factory-frontend/node_modules/.deno/@[email protected]/node_modules/@babel/core/index.js' imported from 'https://jsr.io/@fresh/plugin-vite/1.0.7/src/plugins/deno.ts'
    at https://jsr.io/@fresh/plugin-vite/1.0.7/src/plugins/deno.ts:10:24

If I switch to "nodeModulesDir": "auto" in deno.json, the error is not present anymore.

[lishaduck]

It seems as if this is a known issue https://github.com/denoland/fresh/issues/3509#issuecomment-3370353496

[knotbin]

if this issue isn't fixed yet can we move back to auto on the stable release? #3509 says it's blocked but it's already been implemented and shipped into the stable release, and it breaks all new projects' ability to type-check