1.0 release?
See original GitHub issueShipping a 1.0 release will make it easier for different projects to end up with the same instance of source-map-support
(by relying on dependency deduplication). This would lessen the impact of https://github.com/evanw/node-source-map-support/issues/200.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7
Top Results From Across the Web
Software versioning - Wikipedia
Once the game was fully released, the major version number again reset to 1.0.0.
Read more >1.0.0 - Minecraft Wiki - Fandom
1.0.0 is the first non-development release of Minecraft 1.0 (also known as ... It was released at 9:54:50 p.m. GMT on November 18,...
Read more >Grounded 1.0 Release Schedule - Obsidian Entertainment
Grounded 1.0 will officially launch Tuesday, September 27, 2022, at 10:00 am PT ... we want to share the release map for Grounded...
Read more >What to Expect From Grounded's 1.0 Release - Game Rant
Grounded finally releases next month, and here's what fans of the popular survival game can expect following a successful period of early access ......
Read more >What's Coming To Satisfactory 1.0 and Its "Potential" Release ...
What's Coming To Satisfactory 1.0 and It's "Potential" Release DateRead More BelowToday we're looking at what's coming to Satisfactory 1.0 ...
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
Oh dear.
It might be good to unite all source-map related packages into one organization, which could make it easier to evolve them with each others interests in mind. At this point I think
source-map
needs to be forked to have a synchronous implementation…This needs a 1.0.
None of the versions lower than one can be assumed to be compatible, so no hoisting is possible.
To help developers who rely on your code, we recommend starting your package version at 1.0.0 - About Semantic Versioning