The issue is twofold: - It shows Node compatibility is not a primary concern of Webpack. - It is not a default feature of Webpack. Pretty much every Webpack p

The issue is twofold: - It shows Node compatibility is not a primary concern of Webpack. - It is not a default feature of Webpack. Pretty much every Webpack project will need to include this loader config if you want to (safely) start consuming Node/browserify modules I added the config to the article to detail the additional steps.