Bummer. Maybe nobody actually tested the royale-swf package. I only tested the royale package which we did not publish due to collision with another royale package out there. In the next release we will name the packages apache-royale and apache-royale-swf.
Do you have time to try to fix it? Running "ant release" builds packages in the "out" folder. Or you can commit changes, and wait for the nightly build. In theory, instead of running "npm install royale-swf", you can swap in the path to your out folder or the url to the nightly build package instead of "royale-swf". If you don't really need SWF support, you can try npm on the released bin-js.tar.gz file. Go get the link to the package on the mirrors by hitting this link: http://www.apache.org/dyn/closer.lua/royale/0.9.0/binaries/apache-royale-0. 9.0-bin-js.tar.gz Then try 'npm install -g <link to mirrored package>'. It seemed to work for me. HTH, -Alex On 1/24/18, 9:21 AM, "Josh Tynjala" <[email protected]> wrote: >I get the following console output when I run `npm install -g royale-swf` > >https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com%7C10eefaebf4d64e560dc708d >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524112827939628& >sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0 > >It appears that royale-asjs is missing from the path when running the >`npm/dependencies/download_dependencies.js` script. > >- Josh
