Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
0
Members

How to clean up the source after npm build?

A topic by gmg created Feb 20, 2016 Views: 661 Replies: 2
Viewing posts 1 to 3

I know this is more of a TypeScript / npm question, but it's bugging me and I can't find the answer online.

Basically, I have followed the instructions on the website to clone and build Superpowers Game. I've made a few modifications myself and have built them successfully. The only problem is, my source tree is polluted with all of the generated JS files that npm creates. My GitHub Desktop tells me that I have made all these changes, but they're just part of the build process and shouldn't be synced.

How can I clean up my source tree after running build, so that I can do commits and PRs without hassle?

The project has a .gitignore file so it shouldn't check the .js files for commits.

I think there is a problem with your git client, but i don't know really, I have never used github desktop, but it can be a config problem with it.

OK, now I feel foolish. I never even checked, I just assumed that the JS files would end up polluting my repo, so I was copying my changes over to a clean clone. I knew there had to be a better way. At least know I know how to deal with .DS_Store files. I learning so much from this.