Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Don't commit built files in the repo
See original GitHub issueFiles like assets/scripts/dist/choices.js (and company) are needed to be rebuilt every time. This should not be the case.
Fix
-
Add
filesin package.json to whitelist all the files needed, but do NOT includeassets/scripts/dist/in it. -
Add a
scripts.prepublishin package.json to runnpm run js:build(and whatever else is needed) -
Add
assets/scripts/dist/to.gitignore -
Remove the files using
git rm -rf --cached assets/scripts/dist
What it does
The files will not be in the Git repository anymore.
They are, however, uploaded to npm. Just run npm publish and it will build the files and upload them to the npmjs.com registry.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
If the dist files are removed from the repo, what would be the best way for those who aren’t using node to get the built files?
…by the way, I’m asking this because it’d be much easier for us who would occasionally maintain forks of Choices. We can’t always easily contribute our fixes back, because PR’s here should not have the dist files rebuilt.