Missing dist directory in some NPM packages
See original GitHub issueFollowing latest release (thank you!) I tried to update my packages but it seems some NPM packages do not contain the dist
directory with compiled JS:
- ✅ for example, new version of
core
seems OK: https://cdn.jsdelivr.net/npm/@cloud-carbon-footprint/core@0.8.0/ - ❌
app
,aws
,azure
,gcp
, etc. do not contain thedist
directory (while still being referenced as"main": "dist/index.js",
in package.json): https://cdn.jsdelivr.net/npm/@cloud-carbon-footprint/aws@0.0.2/
Also, some files should certainly not be part of the published packages, such as logs
, coverage
, estimates.cache.json
, etc. Let me know if I can help you, I am happy to participate if needed.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
npm install doesnt create dist folder - Stack Overflow
npm install command installs packages that your project will be using as dependencies. It will create the node_modules directory in your current directory...
Read more >npm package broken, missing dist folder · Issue #3 - GitHub
It looks like package.json refers to "main": "dist/index.js" (permalink), but the NPM release is missing the dist folder.
Read more >package.json - npm Docs
The CommonJS Packages spec details a few ways that you can indicate the structure of your package using a directories object. If you...
Read more >npm-prepare-dist
Start using npm-prepare-dist in your project by running `npm i ... Main package.json file will be copied into your dist folder ...
Read more >Creating a package.json file - npm Docs
json file with values that you supply, use the npm init command. On the command line, navigate to the root directory of your...
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
Hey @vhiairrassary,
Thanks for digging into this. I believe you might be correct on the fact that having them all included in the next changeset PR action will trigger the fix. I had to manually publish them initially on npm and we havent bumped since so that would hopefully explain the problem of no dist as I may not have ran a build before the publish.
We will plan to do another release on Monday and make sure to have each new package bumped to trigger the correct build/publish.
Thanks, Cam
I believe this is fixed with the new release! If you want to confirm I can wait to close out this issue.
Thanks, Victor!