-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
build-storybook failing: Unexpected token: name (Service) #1402
Comments
Same here:
So at line
|
@RonnChyran when I try running your repo, I get an error in running storybook itself even before build-storybook:
For what it's worth, |
@shilman I've fixed the
It seems like at line 110411 there is an untranspiled class declaration class Service {
constructor(rootUrl, serviceName) {
this.getServiceUrl = (...path) => {
return [this.rootUrl, this.serviceName, ...path].join('/');
};
this.rootUrl = rootUrl;
this.serviceName = serviceName;
}
} |
I downgraded too a couple versions and get it working back. Will try to do more precise isolation when I get a bit of time. |
|
Seeing similar issue, upgrading to |
the static build does not use read the babel file in also, our babel preset has recently been updated to use are there still issues with the static build here? |
That's exactly it, the JS is not properly transpiled before being sent to Uglify.
Just tried again Related to #1570 |
|
The issue has been open for a while: #1731 Does anyone want to take a stab at making it work? |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 60 days. Thanks! |
Just in case it is relevant, build-storybook was working ok for me until I swapped from babel to the awesome-typescript-loader. It would be nice to have this fixed, but I can work around it by having our stakeholders look at a running storybook server for now. As always thanks for your work on this awesome project. :) |
Same here. I am using webpack with awesome typescript loader and the
whereas i am using |
Here is what i found out. ○ the It means, that your build produces es6+ code, which is passed to old UglifyJS, hence the error ○ For those, who use No matter the case, one, experiencing |
We replaced the uglify plugin in #2530 Can you please check if the problem is still present in |
The issue was fixed in v3.3.3. Thank you. |
In case anyone is seeing this issue after |
Whenever I try to build my project with
build-storybook
, I get the following error:Here is my repo for repro
The text was updated successfully, but these errors were encountered: