-
Notifications
You must be signed in to change notification settings - Fork 161
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
Production build bug with latest node version #5028
Milestone
Comments
I'm having exactly the same issue. I have reporrted this also in #4888 which may be related? |
caalador
pushed a commit
that referenced
this issue
Jun 14, 2019
Apparently this should have been fixed with #5891 |
This was referenced Jan 2, 2023
This was referenced Jan 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem appears when I try to build for production
I use vaadin-maven-plugin configuration to auto detect tools installed on my machine:
<autodetectTools>true</autodetectTools> <nodePath>C:\Program Files\nodejs\node.exe</nodePath> <yarnPath>C:\Program Files (x86)\Yarn\bin\yarn.cmd</yarnPath>
This is the error stack trace:
[INFO] Running 'gulp build_es6' in path\to\project\target\frontend [ERROR] internal/util/inspect.js:31 [ERROR] const types = internalBinding('types'); [ERROR] ^ [ERROR] [ERROR] ReferenceError: internalBinding is not defined [ERROR] at internal/util/inspect.js:31:15 ...
I have installed the latest version of node(10.15.1) an yarn(1.13.0)
I found a workaround: downgrade the node version to 8.15.0 and the build will pass, but I don't understand why with latest version it doesn't works.
Can anyone explain, why?
The text was updated successfully, but these errors were encountered: