Om, That error implies that js.swc or playerglobal.swc/airglobal.swc isn't being found. See if NPM install is putting them in the right place.
Then, those SWCs have to be referenced by whatever -config.xml file in being used, and there are sensitivities in 0.8.0 with dual mode about whether you specify SWCs on library-path, js-library-path or swf-library-path. Same for external-library-path. So the answer may be more in the -config.xml files rather than which files if js/libs does in fact hold the typedefs SWCs. HTH, -Alex On 9/5/17, 11:22 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: >I am trying to debug a problem with Visual Studio Code integration. The >FlexJS 0.8.0 SDK that I installed with `npm install flexjs -g` does not >work with VSCode. It fails with this error: >Error: Missing builtin type Object (1,1) > >More details here: >https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co >m%2FBowlerHatLLC%2Fvscode-nextgenas%2Fissues%2F122&data=02%7C01%7C%7Cb320b >ed7ea2d4c6cac7408d4f48b1ae3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6 >36402325663950518&sdata=uA6c%2BKgpD8QPp3OB1okhwi%2BaprFJfZPkALgsX9gunx0%3D >&reserved=0 > >Then I tried the same with the Installer installed version of FlexJS 0.8.0 >and it seems to work fine. > >Here is a folder diff of the two installations: >https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fibb.co%2F >j2berv&data=02%7C01%7C%7Cb320bed7ea2d4c6cac7408d4f48b1ae3%7Cfa7b1b5a7b3443 >8794aed2c178decee1%7C0%7C0%7C636402325663950518&sdata=BjN9%2BmOgqjFtb2I4YE >ZZURO9XESAYbXVIBXYCkgEoPY%3D&reserved=0 > >Off the bat, I see that the Installer version has a flex-typedefs folder >which is missing in the npm version. Any idea when that was added? It >can't possibly be in the released artifact because they both seem to be >getting it from the same binary package. > >Also, can anyone see anything obvious that could be causing this error? > >Thanks, >Om