-
Notifications
You must be signed in to change notification settings - Fork 11
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
ember-codemod-v1-to-v2 #46
base: main
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,5 @@ | |||
'use strict'; | |||
|
|||
const { addonV1Shim } = require('@embroider/addon-shim'); |
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 looks good as far as avoiding a major SemVer bump goes, provided no other major code changes were required to accommodate the migration.
"ember-page-title": "^6.2.1", | ||
"ember-qunit": "^5.1.2", | ||
"ember-resolver": "^8.0.2", | ||
"ember-source": "~3.25.1", |
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.
We should probably cross 4.0 here + drop support for Node < 16. This is a major bump.
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.
Overall, looks great and the architecture matches my understanding for what the new blueprint looks like.
Core codebase -- no request for changes.
Housekeeping -- bumping to 4.0+ and corresponding updates (node support comes to mind).
https://www.kbsoftware.co.uk/crm/ticket/6649/