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

The bundle generator fails after adding a dev dependency #348

Open
MarkStega opened this issue Jan 10, 2025 · 2 comments
Open

The bundle generator fails after adding a dev dependency #348

MarkStega opened this issue Jan 10, 2025 · 2 comments

Comments

@MarkStega
Copy link

MarkStega commented Jan 10, 2025

Bug report

The bundle generator fails with Error: Something went wrong - getSymbolsUsingSymbol returned null but expected to be a set of symbols (symbol="D:/Miscellaneous/d-b-g-issue/node_modules/@babel/types/lib/index")

I have a complete reproduction in a repository at https://github.com/Material-Blazor/d-b-g-issue. The project is a tiny React library with two toy components. The goal is to create a rollup and an accompanying .d.ts file.

If you clone that repository do the following to reproduce:

  1. Change directory to the cloned root
  2. npm i
  3. npm run build

This will compile, rollup, and generate the .d.ts file with no issue (output is in the .rollup directory)

Now, checkout the branch 'DemonstrateIssue' and do the following:

  1. delete the .rollup directory
  2. npm update
  3. npm run build

And observe that the bundle generator fails with the opening message. The only change is the addition of two dev dependencies in package.json.

@timocov
Copy link
Owner

timocov commented Jan 10, 2025

Can you try this approach #347 (comment) if see if it helps?

@MarkStega
Copy link
Author

MarkStega commented Jan 10, 2025

"types": [] added to my tsconfig & I no longer have the error. You may want to add a note to that effect in the readme since at least two of use have tripped on this...

Thanks for the very prompt response!

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