Include dist folder for npm installation
See original GitHub issueI tried adding osd as an npm package using the github URI:
"openseadragon": "git://github.com/openseadragon/openseadragon.git",
However, there is no /dist
folder containing the build. Are there any plans to include this?
On npmjs.com the latest version is 2.2.0 not 2.2.1. I prefer to bypass the npm registry whenever possible though.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Role of the src and dist folders in NPM packages
I want to use the method customPATCH. I can see it in the Restangular src/ directory here. However when I ran 'npm install...
Read more >npm-prepare-dist
Clean and prepare dist folder and all files before publishing your NPM library. Potentially smaller build and faster installation of your ...
Read more >Node: How to handle your dist files | by Ikechi Michael - Medium
In your package.json, you can add a “files” property which has an array value and link to the generated files to include them...
Read more >NPM Install with just GitHub - Gleb Bahmutov
I have discussed how to Use GitHub instead of NPM to share and install ... The built dist folder is the one published...
Read more >"dist" folder not created while doing a npm install - jQuery UI
The npm module isn't supposed to contain a dist folder. If you want minified files, you should generate them yourself using whatever process...
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
See PR #1258
@dlong500 Sounds good to me! Would you be up for making a patch to do this?
My concern with adding a
dist
was that I don’t want a built copy to reside in this repository (which would be error prone and noisy), but setting it up so it’ll build after fetch is a great solution.We’d probably want to update the documentation somewhere to illustrate this use case. Maybe in the download section on the home page?