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
{{ message }}
This repository has been archived by the owner on Mar 23, 2024. It is now read-only.
As I understand it, require.js' paths config lets you create local aliases and prefixes for local dependencies.
However, the requirejs_include_tag helper only makes the paths config available in the rendered javascript, if that path is an absolute URL (or an array of fallback URLs)
If I want my modules to depend on jQuery and have that linked to this correctly versioned file, I'd expect to be able to use config like this:
paths:
jquery: 'jquery-1.12.0'
…but (as described above) this config never makes it to the browser. What am I doing wrong?
I should note that, if I remove the if condition from the line I linked above then I do see the config rendered and everything works properly, but I guess there must be some other reason for that condition to be there, I just don't know what it is.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As I understand it,
require.js
'paths
config lets you create local aliases and prefixes for local dependencies.However, the
requirejs_include_tag
helper only makes the paths config available in the rendered javascript, if that path is an absolute URL (or an array of fallback URLs)If I want my modules to depend on jQuery and have that linked to this correctly versioned file, I'd expect to be able to use config like this:
…but (as described above) this config never makes it to the browser. What am I doing wrong?
I should note that, if I remove the
if
condition from the line I linked above then I do see the config rendered and everything works properly, but I guess there must be some other reason for that condition to be there, I just don't know what it is.The text was updated successfully, but these errors were encountered: