Skip to content
This repository was archived by the owner on Jun 10, 2018. It is now read-only.

add package.json to search path for packages that do not use bower.json#484

Closed
shioyama wants to merge 1 commit into
sstephenson:masterfrom
shioyama:package_json
Closed

add package.json to search path for packages that do not use bower.json#484
shioyama wants to merge 1 commit into
sstephenson:masterfrom
shioyama:package_json

Conversation

@shioyama

Copy link
Copy Markdown

A lot of packages use package.json instead of bower.json, but AFAICT the basic setup is the same, with the main file indicated under main.

Maybe I'm missing something but it would seem useful to add package.json to the search path as I have here, to handle that case.

@josh

josh commented Oct 11, 2013

Copy link
Copy Markdown
Contributor

Sorry, package.json is conflated with node.js which is why other package managers such as bower (which did originally use it) moved away.

👎

@shioyama

Copy link
Copy Markdown
Author

I figured that was the reason, but is there a concrete scenario where this would cause problems? The only alternative I can see is to track down the maintainers of every package and get them to add a bower.json file.

@josh josh closed this Feb 9, 2014
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