Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Compilation) error RollupError: Expected '{', got 'interface' / token 'static' . Expected * for generator, private key, identifier or async #1690

Open
LaserKaspar opened this issue Feb 27, 2024 · 2 comments

Comments

@LaserKaspar
Copy link

LaserKaspar commented Feb 27, 2024

  • Rollup Plugin Name: @rollup/plugin-dynamic-import-vars
  • Rollup Plugin Version: 2.1.2
  • Rollup Version: v4.9.6
  • Operating System (or Browser): Windows
  • Node Version: v20.9.0
  • Link to reproduction (⚠️ read below): https://github.com/Stirling-Tools/Stirling-PDF/tree/v2-wip (cd ./server-node && npm run dev - Sadly I don't have anything better to reproduce this, sorry...)

Expected Behavior

Dev: Compiles without pressing CTRL-S in a random ts file.
Prod: Compiles

Actual Behavior

Dev: Compiles only after pressing CTRL-S in a random ts file.
Prod: Doesn't compile

Additional Information

When running cd ./server-node && npm run dev the build fails:
image

When I press CTRL-S in a random file (to keep it the same for all of us I chose ./server-node/index.ts) without even modifying it the dev build magically works again. The error doesn't happen when ./shared-operations/src/workflow/operatorAccessor.ts:11 is commented:
image
Or the imported files are removed/commented. (./shared-operations/src/functions/*)
The only file that doesn't produce an error is functions/index.ts

Only index.ts -> no error
Only impose.ts -> error
Only impose.ts with content of index.ts -> error

So the error seems to be dependent on the name of the file for some reason?

Depending on the files present there is another error:
image

Thank you for your time!

@gtalk-renato
Copy link

I have the same problem. Any solution?

@LaserKaspar
Copy link
Author

I have the same problem. Any solution?

How did you cause it? Maybe you could help reproduce it reliability?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants