If npm is broken and it's require fix in the source I understand. What's with second option ? For this release we could provide on the website at least links.
Thanks, Piotr 2018-01-24 19:33 GMT+01:00 Alex Harui <[email protected]>: > I'm not sure how to fix the npm issues without changing a source file. > Any ideas? > > Get Outlook for Android<https://aka.ms/ghei36> > > ________________________________ > From: Piotr Zarzycki <[email protected]> > Sent: Wednesday, January 24, 2018 10:17:12 AM > To: [email protected] > Subject: Re: Cannot install royale-swf from npm > > Alex, > > Can we republish once again everything ? If not can we upload binaries to > Apache mirrors[1] as we had this with Flex ? > > [1] > https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4. > 16.1%2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02% > 7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6% > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&sdata= > KS5MwWOTANwoaf9iihN2CBWFtTfOgUKfNBRMr5qb%2Blc%3D&reserved=0 > > Thanks, > Piotr > > > 2018-01-24 19:11 GMT+01:00 Alex Harui <[email protected]>: > > > 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: > > > > https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale% > 2F0.9.0%2F&data=02%7C01%7Caharui%40adobe.com% > 7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq% > 2F2nxga4gg309Oh48I%3D&reserved=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 > > > > > > > -- > > Piotr Zarzycki > > Patreon: *https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01% > 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6% > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&sdata= > SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0 > <https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01% > 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6% > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877&sdata= > SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>* > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
