-
Notifications
You must be signed in to change notification settings - Fork 25
Drop Node.js 6 support #80
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
Conversation
1e18c5a to
379922b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove these files:
services/account/package-lock.jsonservices/customer/package-lock.jsonservices/facade/package-lock.jsonservices/todo-legacy/package-lock.jsonservices/transaction/package-lock.json
Other than that, I don't see any obvious problems.
|
Oh, please check why |
LOL, I got confused when reading the diff. Your pull request is already removing those package-lock files, that's great! So the only blocker is the fact that the only CI we have configured (cis-jenkins) is failing. |
kjdelisle
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor fixes required, but almost ready to land.
| { | ||
| "ids": { | ||
| "Account": 17 | ||
| "Account": 23 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This value shouldn't have changed (technically, this test needs rewriting because this value shouldn't be perpetually increasing in commits!).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be clear; don't rewrite the test logic as a part of this commit. Just revert this change.
|
Tests are failing due to this issue: Are you seeing this compilation failure locally? |
|
@kjdelisle @bajtos it was passing fine on local :(, but will fix those up. on a side note, @shimks and I were trying to figure out where the dist folders were being generated after running the compiler, since they were nowhere to be found. |
| @@ -1,15 +1,17 @@ | |||
| import { api, Application, inject } from '@loopback/core'; | |||
| import { Application, inject } from '@loopback/core'; | |||
| import { api } from '@loopback/rest'; | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@b-admike we export @api from @loopback/rest only for backward compatibility, it is now defined and exported from @loopback/openapi-v2
Not a necessary to change them to @loopback/openapi-v2 in this PR since that package will be renamed in v3 in the near future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure~ 👍
02c8af2 to
e512763
Compare
LoopBack4 is dropping support for Node 6 because it is no longer LTS and doesn't support newer features. It's best for this example repository to align with it. BREAKING CHANGE: Support for Node.js version lower than 8.0 has been dropped. Please upgrade to Node 8 or higher.
e512763 to
a6de58c
Compare
|
@slnode test please |
LoopBack4 is dropping support for Node 6 because it is no longer LTS and doesn't support newer features. It's best for this example repo to align with it.
BREAKING CHANGE: Support for Node.js version lower than 8.0 has been dropped. Please upgrade to Node 8 or higher.
Connect to loopbackio/loopback-next#611