Skip to content
This repository was archived by the owner on Dec 11, 2025. It is now read-only.

Prepare module to be published to npm - #36

Merged
geekdave merged 4 commits into
geekdave:masterfrom
jamiebuilds:patch-1
Apr 7, 2014
Merged

Prepare module to be published to npm#36
geekdave merged 4 commits into
geekdave:masterfrom
jamiebuilds:patch-1

Conversation

@jamiebuilds

Copy link
Copy Markdown
Contributor

It would be really great if backbone.subroute was published on npm. I made all the necessary changes in order to make it work. If you need help, this doc should help you with pretty much everything. If you need any other help, I can probably answer any questions you have.


Changes:

  • Added .npmignore
  • Fixed license url
  • Changed main attribute to correct file (also fixed here)
  • Move backbone from dependencies to devDependencies (explained below)

I moved backbone to devDependencies because backbone should always be a peer dependency. If you declare it, then something like browserify will require two separate backbones (one from their app, the other from your module), which you really don't want.


If you need anything else in this PR, please let me know. Thanks

geekdave added a commit that referenced this pull request Apr 7, 2014
Prepare module to be published to npm
@geekdave
geekdave merged commit c2de57d into geekdave:master Apr 7, 2014
@geekdave

geekdave commented Apr 7, 2014

Copy link
Copy Markdown
Owner

Published here: https://www.npmjs.org/package/backbone.subroute

@jamiebuilds
jamiebuilds deleted the patch-1 branch April 7, 2014 23:33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants