Unable to build TypeScript bundle when outDir is specified in tsconfig.json

[dstaley]

• Rollup Plugin Name: @rollup/plugin-typescript
• Rollup Plugin Version: v4.0.0
• Rollup Version: v1.32.0
• Operating System (or Browser): Windows 10
• Node Version: v12

How Do We Reproduce?

https://repl.it/repls/EnchantingHatefulFunctions

Expected Behavior

Module builds correctly

Actual Behavior

Error: Unexpected token (Note that you need plugins to import files that are not JavaScript)

It looks like this is because the paths stored in emittedFileNames don't match the paths in emittedFiles.

{
  emittedFileNames: [
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/src/index.fx.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/src/index.fx.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/src/index.fx.d.ts'
  ],
  emittedFiles: [Map Iterator] {
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/utils.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/utils.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/utils.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/errors.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/errors.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/errors.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/types.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/types.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/types.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/http.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/http.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/http.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/endpoint.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/endpoint.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/endpoint.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/requests.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/requests.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/requests.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/batch.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/batch.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/batch.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/collection.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/collection.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/collection.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/bucket.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/bucket.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/bucket.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/base.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/base.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/base.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/index.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/index.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/index.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/index.browser.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/index.browser.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/index.browser.d.ts',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/index.fx.js.map',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/index.fx.js',
    'C:/Users/Dylan/Documents/git/kinto/kinto-http.js/lib/index.fx.d.ts'
  }
}

This only happens when tsconfig.json has a outDir property, and removing it results in the bundle being correctly generated. This didn't occur on v3.0.0, so I assume it's related to switching to the BuilderProgram API.

[shellscape]

Give v4.0.0 a shot. We had some issues with how 3.1.0 was published.

[dstaley]

@shellscape Just tested and the issue still occurs on 4.0.0.

[NotWoods]

We've made some adjustments to the plugin and right now we're requiring that outDir be located within your Rollup output dir. Unfortunately the hook that checks this is run after the error is emitted. I'll try to fix this particular case where emittedFileNames and emittedFiles doesn't match.

A quick fix for now is to set compilerOptions.rootDir to "src".

[dstaley]

@NotWoods So I just got around to adding rootDir to my tsconfig, and now get the following error:

Error: Could not load C:\Users\Dylan\Desktop\khttp-rollup-ts\node_modules\tslib\tslib.es6.js (imported by C:/Users/Dylan/Desktop/khttp-rollup-ts/src/base.ts): Debug Failure. False expression: Expected fileName to be present in command line     at Object.getOutputFileNames (C:\Users\Dylan\Desktop\khttp-rollup-ts\node_modules\typescript\lib\typescript.js:92435:18)
    at findTypescriptOutput (C:\Users\Dylan\Desktop\khttp-rollup-ts\node_modules\@rollup\plugin-typescript\dist\index.js:389:33)
    at Object.load (C:\Users\Dylan\Desktop\khttp-rollup-ts\node_modules\@rollup\plugin-typescript\dist\index.js:508:28)     at C:\Users\Dylan\Desktop\khttp-rollup-ts\node_modules\rollup\dist\shared\node-entry.js:13113:25
    at processTicksAndRejections (internal/process/task_queues.js:94:5)

tslib is correctly installed, and I confirmed that the referenced path exists, ,so I'm not sure what it's complaining about. (Also for the record, src/base.ts doesn't import tslib directly.)

[moeriki]

May be related to #249.

I have a reproduction repo that can build with outDir configured.

[daviddelusenet]

For me this is happening because I want to emit declaration files. When I add "outDir": "" to my tsconfig.json I get the following error:

[!] (plugin babel) SyntaxError: /some/path/types.ts: Support for the experimental syntax 'exportDefaultFrom' isn't currently enabled (5:8):

  4 |
> 5 | export enum Alignment {
  6 |

[MR-L-2015]

before bug fixed, use rollup-plugin-typescript2 instead. Works good.

rollup-plugin-typescript2 - npm
https://www.npmjs.com/package/rollup-plugin-typescript2

[gwardwell]

@dstaley I'm experiencing a similar error when trying to use this plugin with Vue.js single file components. Did you find a workaround?

[!] (plugin typescript) Error: Could not load /Users/[USERNAME]/[PROJECT]/src/components/[COMPONENT].vue?rollup-plugin-vue=script.ts (imported by /Users/[USERNAME]/[PROJECT]/src/components/[COMPONENT].vue): Debug Failure. False expression: Expected fileName to be present in command line
Error: Could not load /Users/[USERNAME]/[PROJECT]/src/components/[COMPONENT].vue?rollup-plugin-vue=script.ts (imported by /Users/[USERNAME]/[PROJECT]/src/components/[COMPONENT].vue): Debug Failure. False expression: Expected fileName to be present in command line
    at Object.getOutputFileNames (/Users/[USERNAME]/[PROJECT]/node_modules/typescript/lib/typescript.js:89684:18)
    at findTypescriptOutput (/Users/[USERNAME]/[PROJECT]/node_modules/@rollup/plugin-typescript/dist/index.js:389:33)
    at Object.load (/Users/[USERNAME]/[PROJECT]/node_modules/@rollup/plugin-typescript/dist/index.js:508:28)
    at /Users/[USERNAME]/[PROJECT]/node_modules/rollup/dist/shared/rollup.js:17441:25

[lockinmarv]

@gwardwell Same here. Changed the order of the vue plugin so it's before the ts plugin

[gwardwell]

@MarvinRudolph I tried that and saw the same error. Rearranging corejs to after typescript and Vue plugins ultimately solved it for me.

Thanks for replying!