goog.scope + compiler about closure-loader HOT 2 CLOSED

Hey, thanks for the feedback.

I'm not a big expert on everything closure compiler related as I created this loader specifically to get rid of the closure compiler back in the day when I first created it (the project does not longer exist), so I can't fully answer your question.

That beeing said, this loader merely replaces goog.provide and goog.require with their node counterparts (module.export and require()) with some added namespacing. Thus file be be seen as a module by webpack and thus has its own scope. goog.scope isn't necessary for the actual scoping, as every file is a normal webpack module (like any other regular module in webpack) but the loader doesn't do any of the inlining of aliases etc. that the compiler seems to do within such a scope (this would fall to whatever minification you do with our code).

This loader is generally compatible with the closure library, though every now an then some modules seem to have problems. There were some pull requests (and some are still opened where I sadly haven't come around to check them yet) to fix some of the issues though and you need to add special configuration for that.

As of support for the compiler itself (is there a webpack loader or plugin for that?): I have no idea. I think it should be compatible, but I have never tried myself (and to be honest: I don't intend on doing that).

from closure-loader.

Thanks for the response! I'll close this issue, but def helpful. thanks again

from closure-loader.