The build/ folder isn't published! Version 6.2.1 is broken!
See original GitHub issueHey, somehow on your latest publish the build folder to which points the library when you require it isn’t there --> "main": "build/entry.js",
.
Maybe is it because build
is in the .npmignore, or because the prepublishOnly
hook didn’t work?
Please publish a patch as soon as possible, for the future maybe include the build in the repo, I think it’s safer and many other libraries do it. Or use the files
field in package.json to publish only the build
folder.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
DotNet.publish fails attempting to load Microsoft.Build ... - GitHub
I expect the task to succeed, and the project to be published to the target folder. Actual behavior. The build fails at DotNet:publish...
Read more >Upgrading your build from Gradle 6.x to the latest
This chapter provides the information you need to migrate your Gradle 6.x builds to the latest Gradle release. For migrating from Gradle 4.x...
Read more >Why there is no physical client/build folder when i run nodejs ...
The build folder is only created when the app is in production mode(example:heroku) not in development mode. That is why there is no...
Read more >Known issues with Android Studio and Android Gradle Plugin
To fix this issue, upgrade your Android 11 emulator to version 9 or higher by navigating to Tools > SDK Manager. In the...
Read more >Release notes for the Microsoft JDBC Driver for SQL Server
This article lists the releases of the Microsoft JDBC Driver for SQL Server. For each release version, the changes are named and described....
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 FreeTop 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
Top GitHub Comments
Updated it just now, it works fine! Thank you!
@marcofugaro You should have 6.2.2 published and 6.2.1 marked as deprecated. I manually checked package contents and build folder is back in place. Please confirm whether everything works fine for you.