Type only imports are not set as dependencies

[ezolenko]

After interface modification the plugin (v0.3.0) serves depending files from the cache, missing potentially breaking changes.

To reproduce make a clean build, break a type-only ts file and rerun a build.

[ezolenko]

Might depend on resolution of one of those:
rollup/rollup#1203
rollup/rollup#1248

[yankeeinlondon]

Can't wait to see this included, looks like your blockers are starting to have PR's against them.

[ezolenko]

Also affects watch mode, need to add all files specified by tsconfig to rollup watch list

[posva]

is this error the same:

(!) Import of non-existent export
src/rtdb/utils.ts
1: import { database } from 'firebase';

database is type only and there isn't a real export in the js file:

(!) Error when using sourcemap for reporting an error: Can't resolve original location of error.
src/rtdb/utils.ts: (1:9)
[!] Error: 'database' is not exported by ../../../node_modules/firebase/dist/index.esm.js

[ezolenko]

@posva No, your error looks different. You can't really import anything a module is not exporting. If you want side effects, you can do plain import 'firebase'. What happens if you simply remove that import?

[posva]

If I remove it it doesn't compile because it's missing that database namespace. It's weird because the error only happens for packages/@posva/vuefire-core but not for packages/vuefire (in a learn monorepo). I ended up creating an alias (rollup-plugin-alias) for the firebase package that resolves to a stub that exports empty objects. It suppress the errors with rollup while still getting correct typings output:

[domoritz]

I think this bug causes a problem in my builds as well. I am missing declaration files for files that export only types. Is this captured by this issue? Are there any known workarounds?