-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
requirejs:compile #187
Comments
Hi Jacob, regards, |
Hey Jan it’s not working like that, caused by the duplicate path. maybe the fix from aaronjensen will be a solution. I have built a new version locally with this enhancement but could not get it work yet. I’m more a designer, less developer. I tried almost every possibility without being able to solve the problem. |
Hi Jakob, regards, |
update: it works for me for both the minified and uncompressed version... |
it's not working this way with ‹r.js› because there is a duplication of the paths.
|
Hi Jakob, Please let me know if this does the trick. |
Works like a charm, thank you very much for your support and the fast update! |
yw |
Yes, you can. |
It is possible to load scrollMagic as an AMD with requirejs. As far as I know your solution contains a call of two apps with the duplication of the require.config path—the dirty way. As I use the use-init boilerplate, I have a problem with this kind of solution. The dev version works—although it includes an error. But in the build version it is not possible to get your method work.
Is it possible to separate ScrollMagic and ScrollScene by defining two modules inside your plugin and to enable the use of your tool like that in the future? Or is there any way of using it without calling the path twice?
terminal excerpt:
[Error: Module loading did not complete for: main, modules/scrollMagic, ScrollScene The following modules share the same URL. This could be a misconfiguration if that URL only has one anonymous module in it: /path/init/components/ScrollMagic/js/jquery.scrollmagic.min.js: ScrollScene, ScrollMagic] }
The text was updated successfully, but these errors were encountered: