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
Script names that are just regular paths ending in ".js", start with a "/" or have a protocol in them are always mapped relative to the HTML page instead of relative to baseUrl, just like HTML <script> src="" values.
The optimizer still looks for *.js files using the baseUrl, set in the build config file, as if they were modules. This is different behavior than what require.js does, and so it fails to find them. Instead, it should look for them relative to the project/output directories, or some other special parameter specifically for .js files.
The text was updated successfully, but these errors were encountered:
From http://requirejs.org/docs/api.html#jsfiles :
The optimizer still looks for *.js files using the baseUrl, set in the build config file, as if they were modules. This is different behavior than what require.js does, and so it fails to find them. Instead, it should look for them relative to the project/output directories, or some other special parameter specifically for .js files.
The text was updated successfully, but these errors were encountered: