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.

Can the next version of this package be published to NPM?

See original GitHub issue

Would it be possible to get a new version of tsd-jsdoc published? Several of the changes/fixes that have been committed to the codebase since v2.1.3 was published to NPM would be really useful to have available to us.

Thanks!

Issue Analytics

State:
Created 4 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

englercjcommented, May 18, 2019

v2.2.0 has been published.

0reactions

arizonatribecommented, May 5, 2019

Sure, I suppose, but one of the main advantages semantic versioning is not having to bundle dozens of little patches into one (infrequent) large release. You can save large releases for major changes and continue to publish small patches or minor (non-breaking) feature additions more frequently.

Top Results From Across the Web

Updating your published package version number - npm Docs

Go to your package page ( https://npmjs.com/package/<package> ) to check that the package version has been updated. For more information on npm version...

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...

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

Publishing a beta or alpha version is quite similar to publish a final version. The only difference is the —-tag flag in the...

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 ...

The way the industry publishes (and updates) packages. · Run tests (if there are any) · Update version in package.json according to Semver...