Expose a public API through a global without path aliases? about amdclean HOT 7 CLOSED

To use a "global" instead of a local variable, you just need to set the globalObject option to true.

Also, I am about to add a new option, called prefixTransform, that should help you adjust how AMDClean normalizes (aka prefixes) module names. This option will be included with the next version of AMDClean (I am shooting to release tomorrow).

prefixTransform Example

    amdclean.clean({
        'code': 'var example = require("util/anotherModule");',
        'prefixTransform': function(moduleName) {
            return moduleName.substring(moduleName.lastIndexOf('_') + 1, moduleName.length);
        }
    });

This would result in the following code: var example=anotherModule;

from amdclean.

You can now use the prefixTransform option with the AMDClean 1.2.1 release.

from amdclean.

Hey, elegant solution. Thank you!

from amdclean.

@vonWolfehaus Glad you like it! Does this work for you? Do you need anything else?

from amdclean.

It does work, much appreciated. At least I think so, as what I'm seeing might be another issue entirely. I have an inline require: return require('core/Kai').registerComponents(arguments);. The first part got replaced with core_Kai, and not the expected global-prefixed version, von.core_Kai. It worked before I upgraded to 1.2.1 but maybe I did something different? The repo is here if you want to check out the gulpfile. It looks like a special case, where it's expecting core_Kai to be defined in the arguments array, but it isn't. Any suggestions?

from amdclean.

The file in question is this one, forgot to mention.

from amdclean.

#32

from amdclean.