Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

On Tue, May 1, 2018 at 11:16 PM, Alex Harui wrote: > I think that's a bug in releasecandidate.xml. When you run the release > target, it calls the update.versions target before reminding you to run the > release.npm target. It did not occur to me that the publishing

Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

Hi Alex, package.json which is the default file npm picks up -Dany Op 2 mei 2018 om 06:45 uur uur schreef Alex Harui : OK, but what file would contain that string such that it shows up then? Thanks, -Alex On 5/1/18, 9:32 PM, "OmPrakash Muppirala"

Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

I think that's a bug in releasecandidate.xml. When you run the release target, it calls the update.versions target before reminding you to run the release.npm target. It did not occur to me that the publishing grabbed files other than the tar.gz (which should have the right version in its

Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

As per git history, this file was updated from 0.9.2 to 0.9.3 on 3/16/2018 at around 10:40AM : https://github.com/apache/royale-asjs/commit/2e6923440655c2c2314a9f3e2e1d91fa745cd6e2#diff-6515d4243f4018bb4527c9184823da7f According to https://www.npmjs.com/org/apache-royale, the 0.9.3 release was