Module parse failed: /.../node_modules/any-promise/LICENSE Unexpected token

Hi,

I am building an isomorphic project (code that can run in browser and in node) using webpack, and I am currently facing an weird issue and webpack does not give me enough data to understand what is going on (see stack trace below).

From what I know of webpack, it complains here that there is a dynamic require() (eg: require(var)) so it try to resolve every possible path, and then it breaks on files like LICENSE, README etc…

Warning: %s Critical dependencies:
22:12-28 the request of a dependency is an expression
Warning: %s Module parse failed: /Users/moox/Sync/Development/putaindecode.io/node_modules/any-promise/LICENSE Unexpected token (1:14)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (1:14)
    at Parser.pp$4.raise (/Users/moox/Sync/Development/putaindecode.io/node_modules/acorn/dist/acorn.js:2221:15)
    at Parser.pp.unexpected (/Users/moox/Sync/Development/putaindecode.io/node_modules/acorn/dist/acorn.js:603:10)
    at Parser.pp.semicolon (/Users/moox/Sync/Development/putaindecode.io/node_modules/acorn/dist/acorn.js:581:61)
    at Parser.pp$1.parseExpressionStatement (/Users/moox/Sync/Development/putaindecode.io/node_modules/acorn/dist/acorn.js:966:10)
    at Parser.pp$1.parseStatement (/Users/moox/Sync/Development/putaindecode.io/node_modules/acorn/dist/acorn.js:730:24)
    at Parser.pp$1.parseTopLevel (/Users/moox/Sync/Development/putaindecode.io/node_modules/acorn/dist/acorn.js:638:25)
    at Parser.parse (/Users/moox/Sync/Development/putaindecode.io/node_modules/acorn/dist/acorn.js:516:17)
    at Object.parse (/Users/moox/Sync/Development/putaindecode.io/node_modules/acorn/dist/acorn.js:3098:39)
    at Parser.parse (/Users/moox/Sync/Development/putaindecode.io/node_modules/webpack/lib/Parser.js:902:15)
    at DependenciesBlock.<anonymous> (/Users/moox/Sync/Development/putaindecode.io/node_modules/webpack/lib/NormalModule.js:104:16) +1ms

Why are you using dynamic require? I have a workaround (to use webpack “externals” option) but this is causing me others issues as well, so I would like to know if we can do something over here to avoid this issue in the first place.

[alecmev]

Here’s a quick workaround:

module.exports = {
  plugins: [
    new webpack.NormalModuleReplacementPlugin(/^any-promise$/, 'bluebird'),
  ],
}

What this does is it simply replaces all requires/imports of any-promise with your choice of Promise implementation, e.g. bluebird in my case. If you want to use the native Promise, try some simple polyfill, e.g. pinkie-promise (its index.js is module.exports = typeof Promise === 'function' ? Promise : require('pinkie')), I think Webpack will eliminate the polyfill itself (don’t take my word on it though).

[rsp]

@jeremejevs For the “simple polyfill” part you can try promise-monofill - a simple module that I wrote that always returns the native promise, with no polyfills. It should be even simpler than pinkie.