Do you have any tips on how to migrate legacy webapps to webpack? about ama HOT 3 CLOSED

Personally when I had this kind of task, I just walked over tons of modules and manually reformatted them to be in CommonJS. I'd replace some common patterns via "find and replace" but it was mostly manual work.

from ama.

@winterbe See also exports-loader, which can fix this kind of issue and prevent the leak to global. If most of your modules follow a similar style, you can apply a loader to all of them and fix the issue in your bundle.

This code will create a local variable called window in the module's scope and set it to an empty object so your module is unable to actually export to global. Then, it will add module.exports = window.MyModule to the module so you can use it like a proper commonjs module.

require("imports?window=>{}!exports?window.MyModule!./file.js")

From http://webpack.github.io/docs/shimming-modules.html

from ama.

Thanks for pointing that out. I'll give it a shot.

Am 17.09.2015 um 00:19 schrieb Samuel Reed [email protected]:

@winterbe See also exports-loader, which can fix this kind of issue and prevent the leak to global. If most of your modules follow a similar style, you can apply a loader to all of them and fix the issue in your bundle.

This code will create a local variable called window in the module's scope and set it to an empty object so your module is unable to actually export to global. Then, it will add module.exports = window.MyModule to the module so you can use it like a proper commonjs module.

require("imports?window=>{}!exports?window.MyModule!./file.js")

—
Reply to this email directly or view it on GitHub.

from ama.