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
I tried to update our existing web projects from 2.2.0 to 2.3.0/2.3.1 and get the following errors. I couldn't find a existing issue or something in the change notes that would hint at what could cause this. I'm fine with running 2.2.0, but thought I would share. This is running on Windows 10 with Java 1.8.0_66 (64-bit, Server VM).
jjs -scripting src\main\resources\lib\r.js -- -o build.js dir=target\dist
src\main\resources\lib\r.js:22357:8 In strict mode, function declarations can only occur at program or function body level. You should use a function expression here instead.
function addFile(file, fileUrl) {
^
src\main\resources\lib\r.js:22447:1 Expected , but found ;
};
^
src\main\resources\lib\r.js:22498:1 Expected ; but found )
});
^
src\main\resources\lib\r.js:27768:4 Expected ) but found function
function setBaseUrl(fileName) {
^
src\main\resources\lib\r.js:27778:4 Expected eof but found }
}
^
2.3.1 (Current Master)
jjs -scripting src\main\resources\lib\r.js -- -o build.js dir=target\dist
src\main\resources\lib\r.js:260 ReferenceError: "setTimeout" is not defined
The text was updated successfully, but these errors were encountered:
I think this was caused by a problem with a change in 2.3.0, filed requirejs/requirejs#1588 to track the fix, and I just pushed a change to this repo to include that fix in r.js. You can try it to confirm if it fixes the problem by using the latest r.js snapshot:
I tried to update our existing web projects from 2.2.0 to 2.3.0/2.3.1 and get the following errors. I couldn't find a existing issue or something in the change notes that would hint at what could cause this. I'm fine with running 2.2.0, but thought I would share. This is running on Windows 10 with Java 1.8.0_66 (64-bit, Server VM).
2.2.0 (File Ref)
2.3.0: (File Ref)
2.3.1 (Current Master)
The text was updated successfully, but these errors were encountered: