-
Notifications
You must be signed in to change notification settings - Fork 92
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
[vite:dts] Internal Error: Unable to determine semantic information for declaration #281
Comments
I can't reproduce this issue, refer to https://stackblitz.com/~/github.com/qmhc/react-blogs/tree/qmhc/patch-58131. Maybe you can use a template in stackblitz and create a minimum reproduction. |
Hey, i've made a new branch and you can see the error caused in https://github.com/norvalbv/react-blogs/tree/test The error is still the same, below: :) |
Refer to microsoft/rushstack#3875, this maybe a limitation of Currently you need to use relative paths: export * from './components'; or use alias with {
"compilerOptions": {
"baseUrl": ".",
"paths": {
"src/*": ["./src/*"]
}
}
} export * from 'src/components'; |
I have the same bug with v4. I downgraded to v3 and it was gone. |
@dherault Could you provide a reproduction? |
Describe the bug
`[vite:dts] Internal Error: Unable to determine semantic information for declaration:
/Users/beam/Desktop/Person/react-blogs/src/components/Title/index.tsx:16:9
You have encountered a software defect. Please consider reporting the issue to the maintainers of this application.
✓ built in 3.78s
error during build:
Error: Internal Error: Unable to determine semantic information for declaration:`
When using
dts({ rollupTypes: true })
the plugin does not work when destructuring.For example,
This throws a bug:
this throws a bug:
Etc.
full error:
From some basic research it seems to be an error with Api-Extractor and you may need to downgrade?
Reproduction
https://github.com/norvalbv/react-blogs
Steps to reproduce
Go to any components folder in
/src
and put one of those examples above in the code, then simply running yarn build or yarn build --watch will throw an error.System Info
Validations
The text was updated successfully, but these errors were encountered: