You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Change directory to the cloned root
npm i
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:
delete the .rollup directory
npm update
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.
The text was updated successfully, but these errors were encountered:
"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...
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:
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:
And observe that the bundle generator fails with the opening message. The only change is the addition of two dev dependencies in package.json.
The text was updated successfully, but these errors were encountered: