-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[3.0.0alpha] build-storybook no longer supports relative paths #1052
Comments
Same problem. A possible workaround is: |
Fixes storybookjs#1052 I've tested this locally and it resolves the issue I encountered.
Fixes #1052 I've tested this locally and it resolves the issue I encountered.
how this is is solved? as I still can't have an absolute path in my storybook project.? |
@unutoiul Please explain what's you're trying to do, from what I understand in your comment you're trying to do the opposite of the OP. Here's the fix implemented, by the @ajhyndman himself. (:bow:) Please understand we're just humans here, not mind readers. |
Hi, I'm trying to have absolute path when I import files: example: import Test from 'shared-components/components/test/test'; instead of import Test from './../components/test/test'; Thanks, |
If you want to have some special resolver logic, you need to configure webpack to do so. |
It looks like the build-storybook executable is passing a relative path as-is to Webpack 2 as an output location. Webpack 2 seems to require that this be resolved to an absolute path:
https://webpack.js.org/configuration/output/#output-publicpath
I'd like to see the same relative output pathname supported via command line. Nobody wants an absolute path committed in the
package.json
of their project. I'm hoping this can be resolved programatically inside the webpack config reconciliation?The text was updated successfully, but these errors were encountered: