Security News
NVD Backlog Tops 20,000 CVEs Awaiting Analysis as NIST Prepares System Updates
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
ember-cli-update
Advanced tools
Update Ember CLI Ember.js apps and addons
You can run this either as a global executable available to all projects or an Ember CLI command in a single project.
As a global executable:
npm install -g ember-cli-update
As an Ember CLI command:
ember install ember-cli-update
(You must commit the change to package.json
before running the update command or else you get an error.)
Make sure your git working directory is clean before updating.
Inside your project directory, if you installed globally run
ember-cli-update
or if you installed as a command run
ember update
This will update your app or addon to the latest Ember CLI version. It does this by grabbing your current installed Ember CLI version and looking up the latest version, then applying a diff of the changes needed to your project. Your project files will only get modified if they were changed in the by Ember CLI between versions, and it will only change the section necessary, not the entire file.
This is different from the existing ember init
command. That command tries to reset your project back to a brand new project. It removes all your changes and additions.
You will probably encounter merge conflicts, in which your system's git merge tool will run.
Option | Description | Type | Examples | Default |
---|---|---|---|---|
--from | Use a starting version that is different than what is in your package.json | String | "2.9.1" | |
--to | Update to a version that isn't latest | String | "2.14.1" "~2.15" "latest" "beta" | "latest" |
--ignore-conflicts | Handle merge conflicts yourself | Boolean | false |
Next step is to run codemods when certain upgrades are detected, like ember-source, ember-data, etc. Bonus points if we can figure out how to lazily download said codemods, so we don't have to depend on them all at once (check out lazy-require).
Need help using git mergetool
? Here are some starting points:
If you made a mistake during the update/conflict resolution, run these commands to undo everything and get you back to before the update:
git reset --hard
git clean -f
If you notice ".orig" files lying around after a merge and don't want that behavior, run git config --global mergetool.keepBackup false
.
To avoid being prompted "Hit return to start merge resolution tool (vimdiff):" for every conflict, set a merge tool like git config --global merge.tool "vimdiff"
.
If you are getting an error or unexpected results, running the command with the debug flag:
DEBUG=ember-cli-update,git-diff-apply ember-cli-update
set DEBUG=ember-cli-update,git-diff-apply && ember-cli-update
DEBUG=ember-cli-update,git-diff-apply ember update
set DEBUG=ember-cli-update,git-diff-apply && ember update
will give you more detailed logging.
FAQs
Update Ember CLI projects
The npm package ember-cli-update receives a total of 3,767 weekly downloads. As such, ember-cli-update popularity was classified as popular.
We found that ember-cli-update demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.