JS project loads Royale libs

The JS project, like the one in the wiki, always load the Royale libs.

MXMLJSC
+royalelib=...

Those libs can interfer with the Javascript project classes.

[joshtynjala]

I’m making a few commits to the Royale compiler that should help clear up these exceptions. You’ll be able to try a nightly build soon that I think will work better.

[joshtynjala]

After there’s a nightly build of Royale with my new compiler changes, you should change your asconfig.json for playerglobal.js library to look like this:

{
	"type": "lib",
	"config": "js",
	"compilerOptions": {
        "targets": [
            "SWF",
            "JS"
        ],
        "include-sources": [
            "sources/main/actionscript",
            "sources/main/javascript"
        ],
        "output": "bin/playerglobalJS.swc"
    }
}

(Your PlayerglobalTester asconfig.json file is fine… it actually doesn’t need to specify targets, but it won’t hurt)

It’s not strictly required, but at least when you’re working on that project, all of the Royale UI components will be hidden from code intelligence.

Previously building a SWC with "config": "js" was failing, but that was one of the bugs that I just fixed in the compiler.