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.
Please publish a 1.0.0
See original GitHub issueI think this has reached 1.0.0-worthy.
The current 0.0.x versioning is also a slight PITA because npm install --save tmp will save an exact version, rather than using the user’s designated semver prefix e.g. ~ or ^.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:12
- Comments:19 (5 by maintainers)
Top Results From Across the Web
Please publish against ZIO 1.0.0-RC12-1 #30 - GitHub
Attempting to bump the dependency from interop-reactive-streams to zio-stream % 1.0.0-RC12-1 cause a compile error due to the disappearance of ...
Read more >VSTS task error when run integration tests in .Net Core 2.1
Publish your project. This makes sure that the test dll and all the dependencies get dropped in a folder. You can give path...
Read more >@lerna/publish - npm
Publish packages in the current project. Latest version: 6.3.0, last published: 3 days ago. Start using @lerna/publish in your project by ...
Read more >Publishing Extensions - Visual Studio Code
Learn how to publish Visual Studio Code extensions to the public Marketplace and share them with other developers.
Read more >Preview channel release notes for the Windows App SDK
The preview channel provides a preview of the next upcoming stable release. There may be breaking API changes between a given preview ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@silkentrance No problems with me. Supporting current LTS & LTS-1 is a good policy given the predictable release cadence. Users stuck on <4.x can still depend on node-tmp 0.x.
+1 we want to use this library but no 1.0 major version means we might pull in breaking changes if we use
~or^?