next-update - Tests if module's dependencies can be updated to latest version

  •        17

Note I no longer maintain Node 0.12/4 compatibility. Please switch to Node 6. Both package.json file and node_modules folder are left unchanged, and now you know that you can safely upgrade both libraries to later versions.


changed-log : 0.13.0
chdir-promise : 0.4.0
check-more-types : 2.24.0
cli-color : 1.2.0
common-tags : 1.4.0
console.json : 0.2.1
console.table : 0.8.0
debug : 2.6.8
deps-ok : 1.2.0
easy-table : 0.3.0
execa : 0.7.0
is-online : 5.1.2
lazy-ass : 1.5.0
lodash : 3.10.1
npm-utils : 1.7.1
optimist : 0.6.1
pluralize : 5.0.0
q : 2.0.3
quote : 0.4.0
ramda : 0.24.1
request : 2.74.0
semver : 5.3.0
update-notifier : 0.5.0



Related Projects

semantic-release - :package::rocket: Fully automated version management and package publishing

  •    Javascript

semantic-release automates the whole package release workflow including: determining the next version number, generating the release notes and publishing the package. This removes the immediate connection between human emotions and version numbers, strictly following the Semantic Versioning specification.

rdb - Javascript ORM

  •    Javascript

ORM for nodejs. Supports postgres, mySql and sqlite. 1.7.1 Support for schemas (postgres only). 1.7.0 sqlite3 is now a peer dependency. Add it to your own package.json if you intend to use it. 1.6.9 Bugfix: one-to-many relation returns empty if strategy is included. 1.6.8 Bugfix: one-to-many relation returns empty if insert/update is done earlier in transaction. 1.6.7 Bugfix in relations. 1.6.6 Bugfix. 1.6.5 Improved performance on relations. 1.6.4 Bugfix. 1.6.3 Bugfix: potential incorrect timeZoneOffset when serializing date to JSON. Got timeZoneOffset from now() instead of on actual date. 1.6.2 Removed es6 syntax to ensure backwards compatability. Fixed global var leak. 1.6.1 Now supporting sqlite. 1.6.0 Bugfix: potential ambigous column error when using limit and relating to other tables. 1.5.9 Bugfix: using multipleStatements in mySql could sometimes cause an error when updates are run right before a select. Improved performance on limit when relating to other tables. Using uuid instead of node-uuid Updated all dependencies but generic-pool to latest. (Generic-pool has some breaking changes in latest. I will update it in next release.) 1.5.8 Cleanup line breaks in documentation. 1.5.7 Bugfix: getById.exclusive and tryGetById.exclusive did not lock if row was cached. Improved performance on tryGetFirst. 1.5.6 Raw sql filters can accept sql both as string and as function. E.g. var filter = {sql: function() {return 'foo > 1';}}. 1.5.5 Optional locks for getMany, tryGetFirst and tryGetById. Instead of calling getMany(params) just call getMany.exclusive(params). Same syntax goes for tryGetFirst and tryGetById. This will result in SELECT FOR UPDATE. Bugfix: bulk deletes now accepts raw sql filters too. 1.5.4 Transaction locks. Postgres only. 1.5.3 Upgraded to pg 6.0.3 1.5.2 Improved performance and reduced memory footprint. 1.5.1 Documented JSON column type. Bug fix: Insert and foreign key violation. 1.5.0 JSON column type. Postgres json type does not support rdb filters. 1.4.1 Empty filter would sometimes cause invalid filter. 1.4.0 Raw SQL query. 1.3.0 getMany() now supports limit and orderBy - same syntax as in streaming. 1.2.3 Bugfix: iEqual gave incorrect sql when parameterized. 1.2.2 Exlusive no longer returns a clone of table. It has changes current table to exclusive locking. 1.2.1 Bugfix: Exclusive row locks 1.2.0 Exclusive row locks 1.1.0 Now supporting streaming. Requires postgres or MySQL >=5.7.7 1.0.8 README fixup. 1.0.7 Better performance on insert and update. 1.0.6 Bugfix: Transaction domain should not forward rdb singleton from old domain. 1.0.5 Documentation cleanup. 1.0.4 orderBy in toDto(). 1.0.3 toDto() using next tick on every thousandth row to avoid maximum call stack size exceeded. 1.0.2 Reduced number of simultaneous promises in order to avoid maximum call stack size exceeded. 1.0.1 Bugfix: Incorrect insert/updates on timestamp without timezone. The time was converted utc instead of stripping the timezone. 1.0.0 Transaction domain forwards properties from old domain. Semantic versioning from now on. 0.5.1 Improved performance 0.5.0 Logging: rdb.log(someFunc) logs sql and parameters. Raw sql filters. 0.4.9 New method: tryGetById. New filter: iEqual, postgres only. Bugfix: rows.toJSON() without strategy did not include any children. 0.4.8 Explicit pooling with size and end(). Bugfix: mySql did not release client to pool. 0.4.7 Upgraded to pg 4.3.0 Upgraded to mysql 2.5.5 0.4.6 Upgraded pg 4.2.0. 0.4.5 Oops. Forgot to use pg.js instead of pg. 0.4.4 Upgraded all dependencies to latest. Using pg.js instead of pg. 0.4.3 Can ignore columns when serializing to dto. 0.4.2 Bugfix: update on a row crashes when a delete occurs earlier in same transaction. 0.4.1 Bugfix: more global leaks. 0.4.0 Bugfix: global leak. 0.3.9 Bugfix: eager loading joins/hasOne with non unique column names was not handled correctly. 0.3.8 Supports mySql. Bulk deletes. 0.3.7 Bugfix: eager loading manyRelation on a join/hasOne returned empty array #11 0.3.6 Fixed sql injection vulnerability. 0.3.5 Built-in fetching strategies for lazy loading. Works best in readonly scenarios. 0.3.4 Docs and examples split moved to separate file. 0.3.3 Fixed documentation layout again. 0.3.2 Fixed documentation layout. 0.3.1 Case insensitive filters: iStartsWith, iEndsWith and iContains. 0.3.0 Fix broken links in docs. 0.2.9 Support for row.delete(). Rollback only throws when error is present. 0.2.8 Guid accepts uppercase letters. Bugfix: null inserts on guid columns yielded wrong sql. 0.2.7 New method, toDto(), converts row to data transfer object. Bugfix: toJSON returned incorrect string on hasMany relations. 0.2.6 Fixed incorrect links in README. 0.2.5 Bugfix: caching on composite keys could give a crash #7. Improved sql compression on insert/update. 0.2.4 Bugfix: getMany with many-strategy and shallowFilter yields incorrect query #6. 0.2.3 Reformatted documentation. No code changes.

semver - Semantic Versioning (semver) library written in golang

  •    Go

semver is a Semantic Versioning library written in golang. It fully covers spec version 2.0.0. Note: Always vendor your dependencies or fix on a specific version tag.

eslint-plugin-node - Additional ESLint's rules for Node.js

  •    Javascript

Note: It recommends a use of the "engines" field of package.json. The "engines" field is used by node/no-unsupported-features/* rules. eslint-plugin-node follows semantic versioning and ESLint's Semantic Versioning Policy.

resume-schema - JSON-Schema is used here to define and validate our proposed resume json

  •    HTML

We are still currently un-versioned, some core changes are being pushed out, and a version 0.0.0 will be released following Semantic Versioning 2.0.0 best practices. We will be experimenting with a migration.js system, where each change below will be represented with a function that can update an older version of resume.json to the newer versions. There will be a learning curve for the next few months as to how the ecosystem will revolve around versions.

php-semver-checker - Compares two source sets and determines the appropriate semantic versioning to apply

  •    PHP

PHP Semantic Versioning Checker is a console/library which allows you to inspect a set of before and after source code. After the inspection is completed, you are given a list of changes that have occurred between the two changesets following Semantic Versioning 2.0.0. For each of these changes, the level of the change (MAJOR, MINOR, PATCH) will be given, as well as the location of the change (file and line number) and a reason as to why this level change is suggested.

GitVersion - Easy Semantic Versioning ( for projects using Git

  •    CSharp

Versioning when using git, solved. GitVersion looks at your git history and works out the semantic version of the commit being built.GitVersion works on Mac, Linux with Mono and Windows.

update-notifier - Update notifications for your CLI app

  •    Javascript

Inform users of your package of updates in a non-intrusive way.Whenever you initiate the update notifier and it's not within the interval threshold, it will asynchronously check with npm in the background for available updates, then persist the result. The next time the notifier is initiated, the result will be loaded into the .update property. This prevents any impact on your package startup performance. The update check is done in a unref'ed child process. This means that if you call process.exit, the check will still be performed in its own process.

npm-check-updates - Find newer versions of package dependencies than what your package

  •    Javascript

npm-check-updates upgrades your package.json dependencies to the latest versions, ignoring specified versions. npm-check-updates maintains your existing semantic versioning policies, i.e., it will upgrade your "express": "^4.0.0" dependency to "express": "^5.0.0".

gulp-bump - Bump any version in any file which supports semver with gulp (

  •    Javascript

gulp-bump v2 supports Any valid semver in any filetype. ####You can view more examples in the example folder.

semver - Semantic versioning utilities with the addition of version constraints parsing and checking

  •    PHP

Semver library that offers utilities, version constraint parsing and validation. Originally written as part of composer/composer, now extracted and made available as a stand-alone library.

updtr - Update outdated npm modules with zero pain™

  •    Javascript

Based on npm outdated, updtr installs the latest version and runs npm test for each dependency. In case the test succeeds, updtr saves the new version number to your package.json. Otherwise, updtr rolls back the conflicting update. Additionally, it will use yarn instead of npm when a yarn.lock file is present in your project.

semver - Semantic Versioning Specification


Semantic Versioning Specification

node-semver - The semver parser for node (the one npm uses)

  •    Javascript

The semantic version parser used by npm.


  •    Shell

Virtual Environments for Node.Switch out your node version and global npm install space in one command. Supports named environments. Uses subshells by default so that you can ^D or exit out of an environment quickly. No need to edit .bashrc or .profile, just install and go.

omniauth-saml - A generic SAML strategy for OmniAuth

  •    Ruby

We tag and release gems according to the Semantic Versioning principle. In addition to the guidelines of Semantic Versioning, we follow a further guideline that otherwise backwards-compatible dependency upgrades for security reasons should generally be cause for a MINOR version upgrade as opposed to a PATCH version upgrade. Backwards-incompatible dependency upgrades for security reasons should still result in a MAJOR version upgrade for this library. For IdP-initiated SSO, users should directly access the IdP SSO target URL. Set the href of your application's login link to the value of idp_sso_target_url. For SP-initiated SSO, link to /auth/saml.

cz-cli - The commitizen command line utility.

  •    Javascript

When you commit with Commitizen, you'll be prompted to fill out any required commit fields at commit time. No more waiting until later for a git commit hook to run and reject your commit (though that can still be helpful). No more digging through to find what the preferred format is. Get instant feedback on your commit message formatting and be prompted for required fields. Now, simply use git cz instead of git commit when committing.

comver - Compatible Versioning: major.minor only


Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR format. Compatible Versioning ("ComVer") is SemVer where every PATCH number is 0 (zero). This way, ComVer is backwards compatible with SemVer.

angular-datatables - DataTables using angular directives

  •    Javascript

The major version of the project (it's using a Semantic versioning) will be synchronized with the major version of Angular. In the first versions of angular-datatables, there is a builder to help with using the directive. However, they seem to have brought more confusion instead. So, starting from version 2, you will need to provide the options directly, like in the DataTable's documentation.

citgm - Canary in the Gold Mine

  •    Javascript

citgm is a simple tool for pulling down an arbitrary module from npm and testing it using a specific version of the node runtime.The Node.js project uses citgm to smoke test our releases and controversial changes. The Jenkins job that utilizes citgm can be found on our CI.