-
-
Notifications
You must be signed in to change notification settings - Fork 297
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
"Attempted to resolveName for an unsupported path" error #902
Comments
@jdelStrother did you ever solve this? I'm running into the same error with storybook 8 |
No, sorry - I decided to stick with storybook 7 till this got worked out |
Hey guys, any idea what is causing this?! Having the same issue suddenly with storybook v8. |
Aw great. I'm having the same exact issue after upgrading to v8. Any idea what might be the cause? I did so many changes to get us on v8. Moving back to v7 would be a problem. |
The issue I found was something about how Vite bundles. We had Babel running directly on the files, but after switching to Vite, that's when the issue first appeared. React-Docgen is erroring when loading a chunk from that bundle. I changed the version of our library to the previous Babel release, and was able to load all the components just fine in v8. This means something about chunked imports is causing the problems in react-docgen. We previously used react-docgen-typescript, and I wonder if it handles those differently. |
Looking into this further, it seems you can actually debug it pretty easily. In That will cause it to run Storybook and your code bypassing that cryptic error message. Now that your code's running, you can actually see the error. In my case, it's something to do with
|
Even more info, Vite is building that chunk funky: It's complaining that Just wanna note I don't even use I have |
I fixed this by removing Vite from the equation and rolling Not sure what Vite chunking is doing, but it's unnecessary for this library. Hopefully, that helps someone else! |
react-docgen seems to fail on this file:
producing:
I'm using react-docgen 7.0.3. Curiously, the docgen playground doesn't throw an error on the same file, correctly reporting that it doesn't have a component definition.
Replacing the object-function-shorthand with arrow functions seems to sidestep the issue:
The text was updated successfully, but these errors were encountered: