Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Publish new version to npm

See original GitHub issue

Since dependancy on dom-event was removed, it would be good to also push new version to npm.

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:5 (3 by maintainers)

Top GitHub Comments

2reactions

niksycommented, Mar 29, 2016

https://www.npmjs.com/package/combokeys still says 2.4.4.

0reactions

magnudaecommented, Mar 30, 2016

Thank you @winhamwr!

Top Results From Across the Web

Updating your published package version number - npm Docs

To change the version number in package.json , on the command line, in the package root directory, run the following command, replacing <update_type>...

How to Publish an Updated Version of an npm Package

The easiest way to update your version number is to use the handy npm version command. This will automatically update the version number...

How do I update an NPM module that I published?

Go to your package page (https://npmjs.com/package/) to check that the package version has been updated. Share.

How to publish packages to npm (the way the industry does ...

Run tests (if there are any) · Update version in package.json according to Semver · Create a git tag according to Semver ·...

Publishing a beta or alpha version to NPM | by Kevin Kreuzer

You can run npm version 3.1.0-beta.0 to update package.json and create a git tag in one go (see https://docs.npmjs.com ...