When reading the npm-developers documentation I either
misunderstood/misread/was being an idiot and failed to properly test my
packaging. I believe that I did a test install of the package by
installing from the directory instead of the packaged project (i.e.
.npm/.tgz) itself. As a result I incorrectly assumed that packaging
worked as expected.
When I tried to include the package in another project it was unable to
find the entry point to the package/module as the dist folder didn't
get packaged. This was a result of the .gitignore file being used as
the .npmignore file where the .gitignore file ignores the dist
folder.
I fixed this problem by including a .npmignore file which doesn't
ignore the dist folder. I've confirmed it works also by doing a test
install from the packaged .npm/.tgz.
Version bump: 1.0.0 -> 1.0.1
new file: .npmignore
modified: package.json
When reading the
npm-developersdocumentation I either misunderstood/misread/was being an idiot and failed to properly test my packaging. I believe that I did a test install of the package by installing from the directory instead of the packaged project (i.e. .npm/.tgz) itself. As a result I incorrectly assumed that packaging worked as expected.When I tried to include the package in another project it was unable to find the entry point to the package/module as the
distfolder didn't get packaged. This was a result of the.gitignorefile being used as the.npmignorefile where the.gitignorefile ignores thedistfolder.I fixed this problem by including a
.npmignorefile which doesn't ignore thedistfolder. I've confirmed it works also by doing a test install from the packaged .npm/.tgz.Version bump: 1.0.0 -> 1.0.1 new file: .npmignore modified: package.json