-
Notifications
You must be signed in to change notification settings - Fork 138
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
@nguniversal/express-engine not compatible w/node 8.x #48
Labels
Comments
There's an open issue and PR on |
@theomathieubhvr I'll need to roll back the PR #31 |
fulls1z3
pushed a commit
that referenced
this issue
Aug 2, 2017
fulls1z3
pushed a commit
that referenced
this issue
Aug 2, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 9, 2017
* build(npm): remove package-lock * build: update config * chore(package): update deps Closes (#48)
fulls1z3
pushed a commit
that referenced
this issue
Sep 9, 2017
* chore(package): update deps * build(npm): remove package-lock * build: update config Closes #48
fulls1z3
pushed a commit
that referenced
this issue
Sep 9, 2017
* chore(package): update deps * build(npm): remove package-lock * build: update config Closes #48
fulls1z3
changed the title
[bug] @nguniversal/express-engine is incompatible with node.js 8.x
nguniversal/express-engine is incompatible with node.js 8.x
Sep 16, 2017
fulls1z3
changed the title
nguniversal/express-engine is incompatible with node.js 8.x
@nguniversal/express-engine not compatible w/node 8.x
Sep 16, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a ... (check one with "x")
Current behavior
The dependency @nguniversal/express-engine does not support
node.js v8.x
.Expected/desired behavior
It should support
node.js
platformv8.x
.Minimal reproduction of the problem with instructions
Running either
npm install
oryarn
results with failure.What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Language: [all | TypeScript X.X | ES6/7 | ES5]
Node (for AoT issues):
node --version
=The text was updated successfully, but these errors were encountered: