Cannot find module 'rollup/parseAst' or its corresponding type declarations.

[sagargurtu]

Rollup Version

v4.0.2

Operating System (or Browser)

Chrome

Node Version (if applicable)

No response

Link To Reproduction

https://stackblitz.com/edit/parseast-error?file=src%2Fmain.ts,tsconfig.json

Expected Behaviour

Importing from 'rollup/parseAst' should not throw error.

Actual Behaviour

Importing from 'rollup/parseAst' throws the following error:

Cannot find module 'rollup/parseAst' or its corresponding type declarations.

[lukastaegert]

Unfortunately, this only works if you set "moduleResolution": "node16" (or "bundler") in your tsconfig.json.

[sagargurtu]

"node16" has its own set of issues. Reproduction: https://stackblitz.com/edit/parseast-error-gfgsbm?file=src%2Fmain.ts

See microsoft/TypeScript#50058

Do you have a workaround?

[TrickyPi]

One workaround, Setting "moduleResolution": "Bundler" in your tsconfig.json.

[skhaz]

I am still experiencing this issue. Why has it been closed?

[okinawaa]

me too still experiencing this issue.

[AmorZhao]

Also still experiencing this issue.

[lukastaegert]

I am still experiencing this issue. Why has it been closed?

Because everything is working as intended and setting moduleResolution: "bundler" or "node16" fixes it. If you cannot do that for some reason, you can instead try to import from "rollup/dist/parseAst" or "rollup/dist/parseAst.js", which is the actual file location.

[dirkluijk]

Note that this is breaking for anyone having a TS project with ES modules using rollup as transitive dependency. For example, I am using vitest, which depends on vite, which has an import for rollup/parseAst that breaks for me.

My workaround now is to add a custom mapping in my tsconfig.json:

"paths": {
  // workaround for: https://github.com/vitest-dev/vitest/issues/4567
  "rollup/parseAst": ["./node_modules/rollup/dist/parseAst"]
}

I am not an export in module systems in the JavaScript ecosystem. Should I report this with Vitest?

[dirkluijk]

Never mind, adding "skipLibCheck": true resolved the issue for me and doesn't require any hacky workaround.

[skhaz]

skipLibCheck is a hack IMO.

[jordi-studyportals]

I ran into this issue while using vitest. I got the rollup error because vitest was using vite, so I couldn't change the import.
node_modules/vite/dist/node/index.d.ts:5:41 - error TS2307: Cannot find module 'rollup/parseAst' or its corresponding type declarations.

My problem was caused by tsc because my test folder and vitest.config.ts file were included into the typescript build of my project by accident. I had to add the folder and the vitest.config.ts file to the exluded items in my tsconfig and that resolved the issues for me.

[dirkluijk]

As suggested by @jordi-studyportals, I removed skipLibCheck: true and added "vitest.config.ts" and "**/**.test.ts" to my tsconfig exclude list instead. That did the trick.

[reachAkash]

first set "module" : "ES2015" then "moduleResolution" : "Bundler" in tsconfig.json file. It'll fix the issue, atleast fixed for me.

[skhaz]

Not every project can do those chances.

The wrong here is the library.

[MagdalenaTyminska]

I am still experiencing this issue. Why has it been closed?

Because everything is working as intended and setting moduleResolution: "bundler" or "node16" fixes it. If you cannot do that for some reason, you can instead try to import from "rollup/dist/parseAst" or "rollup/dist/parseAst.js", which is the actual file location.

The problem is, that it doesn't.
At least to me.

If you use the tsconfig by vite then change the file content of "tsconfig.json"

from:

{
  "references": [{ "path": "tsconfig.app.json" }, { "path": "tsconfig.node.json" }]
}

to:

{
  "extends": ["./tsconfig.app.json", "./tsconfig.node.json"]
}

tried this too to no avail.

The other solutions were for vitest which I don't use.

For me the issue still exists and seems there is no working solution to that - at least I haven't found one.

[arevno]

moduleResolution: "bundler" does NOT address this issue for Vite.

[pbalenzuela]

Note that this is breaking for anyone having a TS project with ES modules using rollup as transitive dependency. For example, I am using vitest, which depends on vite, which has an import for rollup/parseAst that breaks for me.

My workaround now is to add a custom mapping in my tsconfig.json:

"paths": {
  // workaround for: https://github.com/vitest-dev/vitest/issues/4567
  "rollup/parseAst": ["./node_modules/rollup/dist/parseAst"]
}

I am not an export in module systems in the JavaScript ecosystem. Should I report this with Vitest?

If you are using pnpm you'll need to point it to a specific version. Ex:

{
  "compilerOptions": {
    "paths": {
      // workaround for: https://github.com/vitest-dev/vitest/issues/4567
      // notice that we'll need to update this when newer versions of vitest are used
      "rollup/parseAst": ["node_modules/.pnpm/rollup@4.21.1/node_modules/rollup/dist/parseAst"]
    }
  },
}