Document the use of vscode-nls with webpack

[PeterWone]

The point of difficulty is in-code use of localize for constructing localised messages.

The question has been raised on Stack Overflow but here are some more details.
In the absence of webpack a trace into this call

const localize = nls.config({ messageFormat: nls.MessageFormat.file })();

reveals that the loader passes a filepath to loadMessageBundle(file)

With webpack this the parameter is undefined. The consequence of this is that things are initialised differently, so a different method is called when I invoke localize, and the default value (the second string parameter passed to localize) is always returned.

Breakpointing the start of loadMessageBundle(file) in an extension that is not bundled (the vscode-nls sample) allows a look at the call stack. The call stack eventually disappears into helper.js inside node.

With webpack in play, the value of this parameter is undefined.

I suspect the problem is that the files generated into the out folder by gulp build are not bundled. They don't even exist in the source so they can't be referenced statically. I have no idea how to convince webpack to include them, or whether this is the whole of the problem.

[dbaeumer]

We should add an example demonstrating how this works.

[TylerLeonhardt]

vscode-nls is deprecated in favor of http://github.com/microsoft/vscode-l10n so closing this.