Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign uppublish co-browser.js to npm #225
Merged
+1
−0
Conversation
|
no, you should just be adding it to the |
|
Done |
|
@jonathanong Can we land this? |
|
+1 |
|
Wait for a moment, @gaye if using browserify, why do you need this file? |
|
It's good to have around for non-browserify, browser consumers |
|
Sound good. |
|
@jonathanong Publish a new patch version to npm? Or add me to the npm owner list too? |
webuniverseio
commented
Oct 5, 2015
|
I don't see co-browser in npm for 4.6.0. Does that mean that files array doesn't work? |
nathanboktae
commented
Dec 16, 2015
|
This fix came in after 4.6.0 @szarouski . Can we get a 4.6.1 / 4.7.0 with this available please? :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
lambdabaa commentedMay 25, 2015
When a repository lacks an
.npmignorefile, npm will fall back on.gitignore. Currently co's.gitignorespecifiesco-browser.jswhich is keeping it from being published to the npm even though it's generated in the prepublish npm step.@jonathanong Looks good?