New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

ember-outdated

Package Overview
Dependencies
Maintainers
1
Versions
3
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

ember-outdated

A CLI tool that shows you what dependencies in an ember-cli project are outdated.

  • 0.1.0-alpha.1
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
1
decreased by-50%
Maintainers
1
Weekly downloads
 
Created
Source

ember-outdated

This command-line tool helps identify which dependencies in an Ember CLI project are out-of-date.

Install

npm install -g ember-outdated@0.1.0-alpha.1

Usage

Simply run ember-outdated from within an Ember CLI application.

$ cd my-awesome-ember-cli-app
$ ember-outdated

Example

Here's the output of running ember-outdated against the frontend for Wordset. ember-outdated for Wordset

How to Interpret

The output of ember-outdated is divided into four columns, Location, Package, Target, Latest, and ember-cli.

  • Location: Either package.json (for npm dependencies) or bower.json (for Bower dependencies).
  • Package: The name of the package.
  • Target: The specific version tag listed in your package.json or bower.json.
  • Latest: The latest non-prerelease version of the package according to npm or bower.
  • ember-cli: If the package is part of Ember CLI's default package.json or bower.json, this column will show the specific version tag for that package.

It's important to note that newer isn't always better, so don't update all your packages just for the sake of updating. Take the time to research each new version, test against your codebase, and determine if you want to upgrade. This is especially true if the latest version is much newer than the target version.

I think something's broken

If something doesn't work the way you think it should, please open an issue! There's small edge cases I know exist, but just haven't run into them myself.

When you open an issue, it would be super helpful if you'd also link to the output of the debug mode, which can be invoked with the --debug flag. HOWEVER, please check the output to make sure there's nothing in it that you don't feel comfortable making public. It returns the raw output of the npm outdated and bower list commands, along with the contents of Ember CLI's package.json and bower.json files.

Working on ember-outdated

If you're thinking about contributing to ember-outdated I'd absolutely love to work with you. However, before making big changes (such as modifying the conditions under which a package is listed as outdated), please open an issue for discussion.

Tests

ember-outdated uses mocha for testing and the Expect/Should assertions from chai. Should is preferred, but Expect can be used where necessary.

Areas for Improvement

Right now the core functionality (that is, the bits of ember-outdated that interface with npm and bower) aren't tested. Breaking up those areas into smaller, more testable units would be awesome.

Keywords

FAQs

Package last updated on 26 Jul 2015

Did you know?

Socket

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.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc