-
Notifications
You must be signed in to change notification settings - Fork 278
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
ui_1 Failed to compile. #1155
Comments
I've seen this before (cf. palantir/blueprint#4112) but didn't realise it affected our production versions. Which version are you running against? |
thats some quick follow-up :) thanks. I git cloned, here is my first line in git log: commit b580a45 (HEAD -> master, tag: 3.7.1, origin/master, origin/HEAD)
I m not super versed in nodejs :) |
awesome. Thank you :) |
Hi,
When trying to do a make all, I get a failed to compile regarding node js module for the ui component:
ui_1 | Starting the development server...
ui_1 |
api_1 | [2020-05-07 18:26:23,009] WARNING:werkzeug: * Debugger is active!
api_1 | [2020-05-07 18:26:23,010] INFO:werkzeug: * Debugger PIN: 208-658-879
ui_1 | Failed to compile.
ui_1 |
ui_1 | ./node_modules/@blueprintjs/core/lib/esnext/components/forms/numericInput.js 60:31
ui_1 | Module parse failed: Unexpected token (60:31)
ui_1 | File was processed with these loaders:
ui_1 | * ./node_modules/babel-loader/lib/index.js
ui_1 | You may need an additional loader to handle the result of these loaders.
ui_1 | | const delta = this.updateDelta(direction, e);
ui_1 | | const nextValue = this.incrementValue(delta);
ui_1 | > this.props.onButtonClick?.(+nextValue, nextValue);
ui_1 | | };
The text was updated successfully, but these errors were encountered: