Originally at 2015-01-26T18:04:18Z by Hannes Hirzel
From chat
Then, add another parameter to the require([...ide-dialog...], ....) call: function () { console.log("IDE loader not detected. Running in production mode."; }
(something like that can be added there by default, in grunt-init-amber)
that second callback will be called when the load failed. the first is called when it succeeded.
(of course, you can just do nothing in the errback, to ignore that ide loader is not present in total silence)
it's up to you what you do, but if you supply second callback, you will handle the error, not requirejs.
Originally at 2015-01-26T18:04:18Z by Hannes Hirzel
From chat
Then, add another parameter to the require([...ide-dialog...], ....) call: function () { console.log("IDE loader not detected. Running in production mode."; }
(something like that can be added there by default, in grunt-init-amber)
that second callback will be called when the load failed. the first is called when it succeeded.
(of course, you can just do nothing in the errback, to ignore that ide loader is not present in total silence)
it's up to you what you do, but if you supply second callback, you will handle the error, not requirejs.
Originally at 2015-01-26T18:04:18Z by Hannes Hirzel
From chat
Then, add another parameter to the require([...ide-dialog...], ....) call: function () { console.log("IDE loader not detected. Running in production mode."; } (something like that can be added there by default, in grunt-init-amber) that second callback will be called when the load failed. the first is called when it succeeded. (of course, you can just do nothing in the errback, to ignore that ide loader is not present in total silence) it's up to you what you do, but if you supply second callback, you will handle the error, not requirejs.