You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
should browserify fall back to the "browser" field when it browserifies B and needs to resolve "url" but doesn't find a "chromeapp" field? It seems like in most cases this would be desirable. What do you think?
The text was updated successfully, but these errors were encountered:
the current behavior is that it'll look for "chromeapp" in the nested dependency (where only "browser" exists), not find it, and resolve to whatever file/module gets used in the regular node.js environment. So basically it ends up handing you non-browserified deps
this is a question. If A depends on B, and their package.json's look like:
A:
B:
when you issue:
should browserify fall back to the "browser" field when it browserifies B and needs to resolve "url" but doesn't find a "chromeapp" field? It seems like in most cases this would be desirable. What do you think?
The text was updated successfully, but these errors were encountered: