The module name within the define statement does not hold any value in the way Plone is using it and can be therefor removed as well. Other than that it is always good to avoid leaking system-specific information to public. Especially when running compile-plone-resources on the same machine serving the Plone site.
I propose to omit this current working directory in the same vein it is done for CSS files in _generate_gruntfile.py.
The compiled JavaScript files contain the current working directory of the time of compilation - see this example (taken from demo.plone.org):
The module name within the define statement does not hold any value in the way Plone is using it and can be therefor removed as well. Other than that it is always good to avoid leaking system-specific information to public. Especially when running
compile-plone-resources
on the same machine serving the Plone site.I propose to omit this current working directory in the same vein it is done for CSS files in
_generate_gruntfile.py
.The result will look then like this:
I'll prepare two PRs for both 1.x and master. Let me know if there are other things to be taken care in this regard.
best, Paul