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
Use the internal require() machinery to look up the location of a module, but rather than loading the module, just return the resolved filename.
had to stub out this function to load browserified browserify, but browserify doesn't implement it (npm doesn't need it, at least to load). Asking for the path of a module doesn't make much sense in a traditional browserify environment because all of the modules are concatenated into one bundle.js file, but it does in webnpm where modules may be present in the webfs.
The text was updated successfully, but these errors were encountered:
http://nodejs.org/api/all.html#all_require_resolve
had to stub out this function to load browserified browserify, but browserify doesn't implement it (npm doesn't need it, at least to load). Asking for the path of a module doesn't make much sense in a traditional browserify environment because all of the modules are concatenated into one bundle.js file, but it does in webnpm where modules may be present in the webfs.
The text was updated successfully, but these errors were encountered: