Skip to content

Conversation

@rgbkrk
Copy link
Member

@rgbkrk rgbkrk commented Nov 27, 2015

For users of the library, this makes it so they don't have to build
our released copy on install straight from npm.

For developers of the library, npm install on a dev copy will run
prepublish (noted npm behavior).

For users of the library, this makes it so they don't have to build
our released copy.

For developers of the library, `npm install` on a dev copy will run
prepublish (noted `npm` behavior).
rgbkrk added a commit that referenced this pull request Nov 27, 2015
@rgbkrk rgbkrk merged commit 367ff74 into master Nov 27, 2015
@rgbkrk rgbkrk deleted the prepublish-build branch November 27, 2015 22:49
@kitten
Copy link
Contributor

kitten commented Nov 28, 2015

We need to revert this. What if someone installs this via git? It is just unclean to publish the package including the lib folder. The build process runs automatically so it shouldn't bother anyone. We could even make it more silent.

@rgbkrk
Copy link
Member Author

rgbkrk commented Nov 28, 2015

The pattern I've been used to is that we publish, directly, lib (while gitignoring it). I've gotten complaints before from people for compiling after an install.

Totally fine to revert and I understand the install from git case. I presume it didn't run that extra step for you then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants