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
The original module is bad for npm since it specifies an AMD module name, which must match the name of the npm package, or else. Since the npm module is called pace-progress, and the AMD module is called pace, a bundler like browserify or webpack won't be able to resolve the dependency.
@benwiley4000 ah ok makes sense. I'm using pace-progress in production with require('imports?define=>false!pace-progress') so yes looks like that's the fix.
The original module is bad for npm since it specifies an AMD module name, which must match the name of the npm package, or else. Since the npm module is called
pace-progress
, and the AMD module is calledpace
, a bundler like browserify or webpack won't be able to resolve the dependency.Removing that from the coffeescript file was great, but I had to run Grunt on my own fork to get it working; the built javascript files still specify an AMD module name.
Thanks 😃
The text was updated successfully, but these errors were encountered: