You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ vue init egoist/vuepack test && cd test
$ npm install && npm run dev
Open the Sources tab in Chrome, and the entire client folder with the full path is shown. I'd expect it to obfuscate that or something, is that expected behavior?
The text was updated successfully, but these errors were encountered:
The full file path is listed in the Sources tab, which just seems weird to me. Shouldnt the webpacking just grab the stuff within that project, but not care what the file path name is? Why would that be preserved anywhere, if the project is just being sent to the /dist folder as static files?
The un-uglified/minified components and the directory structure of the client folder is shown, so someone could basically recreate the project easily.
Even in the client bundle that is minified, the variable names and everything are kept normal.
I am just getting started with webpack and such, but I was under the impression that "uglify" the js meant variable names are replaced with random values, so MySpecialVariable gets turned into acufq everywhere or something like that. Is there ways to accomplish some of this obfuscation with webpack settings?
I understand that the entire client directory will end up being sent to the client's browser but I guess I'm confused as to the level of obfuscation possible.
Scaffold the base project:
Open the Sources tab in Chrome, and the entire client folder with the full path is shown. I'd expect it to obfuscate that or something, is that expected behavior?
The text was updated successfully, but these errors were encountered: