3.8.0 just broke every webpack build that uses 'noParse: [/braintree-web/],' which was the fix to ignore braintree/webpack errors in the console.
3.8.0 now puts the unbundled code on npm, so the noParse hack is no longer needed. The reason it breaks is because now webpack _needs_ to parse it.
I'm going to leave this open for a few days so other people using webpack with the noParse hack will be able to see the solution, then we will close this issue.
+1
Removing the noParse for braintree-web fixed the issue.
Most helpful comment
3.8.0 now puts the unbundled code on npm, so the
noParsehack is no longer needed. The reason it breaks is because now webpack _needs_ to parse it.I'm going to leave this open for a few days so other people using webpack with the
noParsehack will be able to see the solution, then we will close this issue.