This page lists errors that are generated by SeaJS. If the following information does not fix the problem, you can ask on the SeaJS list or open an issue. In either case it is best to have an example or detailed explanation of the problem, hopefully with steps to reproduce.
This error shows up only in some IE browsers. It seldom happens in development phase, and if it occurs, just click the refresh button to fix it.
In production environment, optimization tool should be used in deployment to stop this error from happening.
This error is most likely caused by an incorrect module path. Check the "Net" or "Network" tab in the browser's developer tools to see if there was a 404 error. Make sure the script file is in the right place.
This warning message shows up when there are circular
require() calls. In this case, a module might not be done
being executed when it is returned.
If you have cyclic module dependencies in your program, make sure to plan accordingly.
This error occurs when you try to override an existed alias. It is recommended to use different aliases to stop breaking existed code.
This error occurs when the loader encounters an invalid path such as
http://example.com/../../a.js that can not be resolved to a
correct URL. Make sure all module identifiers are right.