You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Remove dist folder from to git as it is a file automatically generated and we don't need to keep track of them. In that way would be possible to keep the pull requests more clean. To accomplish this just add the dist folderto the gitignore file and add a files property to the package.json specifying the files to be included in the package when download it from npm. Right now all the repo is included.
The only problem that I can see on doing this is that the demo uses a relative path to the dist folder. But the demo can pull the project from a cdn (related #17).
The text was updated successfully, but these errors were encountered:
Remove dist folder from to git as it is a file automatically generated and we don't need to keep track of them.
Removing dist will require folks to implement the build procedure that we've implemented in our project, will seem overkill to new starters, though we can integrate Travis CI to build dist/ folder for us.
add a files property to the package.json specifying the files to be included in the package when download it from npm. Right now all the repo is included.
This should be done, right away.
But the demo can pull the project from a cdn
CDN itself refers to the dist folder minified file.
though we can integrate Travis CI to build dist/ folder for us.
The best way to do it is add a prepublish script to package.json that run the build script. So even the dist being ignored by git, npm include it at the package.
Remove dist folder from to git as it is a file automatically generated and we don't need to keep track of them. In that way would be possible to keep the pull requests more clean. To accomplish this just add the dist folder to the
gitignore
file and add a files property to thepackage.json
specifying the files to be included in the package when download it from npm. Right now all the repo is included.The only problem that I can see on doing this is that the demo uses a relative path to the dist folder. But the demo can pull the project from a cdn (related #17).
The text was updated successfully, but these errors were encountered: