-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
almond integration #3
Comments
Mhh, could you try to replace the "module" property in the "replaceRequireScript" property with the name of the main module?! Yours: replaceRequireScript: [{
files: ['index.html'],
module: '/js/main-built'
}] How i think that it should look like: replaceRequireScript: [{
files: ['index.html'],
module: 'main'
}] Please tell me if that helped. Regards. |
That doesn't help. Currently that property is ignored, only the files property is used. |
Ahh, got it. |
You are now able to add a 'modulePath' configuration setting to your replaceRequireScript config. Hopefully that helps: replaceRequireScript: [{
files: ['index.html'],
module: 'main',
modulePath: '/js/main-built'
}] I don´t know if we get rid off all your issues, but this might be a step towards. |
That fixes the almond aspect, but I still have the other problem mentioned above:
Actually |
Just a guess, |
That works! Dunno why, but that's okay. Maybe add wrap:true to the example in the readme? |
Yeah, snd. time a hear from someone using the plugin successfully :D I don´t know why, in my configuration, if i add wrap=true, i get some weird errors. Nevertheless, |
This is more of a support request then a bug report. I've got pretty far along, though can't get the almond integration working.
My config looks like this:
There are multiple issues:
replaceRequireScript
withalmond:true
has no effect, even though it would still be useful in this setupmodule
property of items in thereplaceRequireScript
array is ignored, though I'd like that to be used for the src-attribute in tasks/require.js:146require
. If I change that to usedefine
, I don't get an error, but nothing is executed.So close...
The text was updated successfully, but these errors were encountered: