OK, I've seen beta9 put the files in the right place on Mac and Win. I didn't
have time to do any further testing.
-Alex
On 9/11/19, 11:06 AM, "Alex Harui" wrote:
Om, how much testing did you do before committing? I finally ran on
Windows and no errors, but the AIR SDK did not get copi
Om, how much testing did you do before committing? I finally ran on Windows
and no errors, but the AIR SDK did not get copied to where it should be.
Thanks,
-Alex
On 9/11/19, 8:25 AM, "OmPrakash Muppirala" wrote:
On Tue, Sep 10, 2019, 11:25 PM Alex Harui wrote:
> Om, why did yo
On Tue, Sep 10, 2019, 11:25 PM Alex Harui wrote:
> Om, why did you change the path to download_dependencies.js in the js-swf
> package.json? Changing it back gets the script to run for me on Mac.
Ah I guess I was trying to fix things locally and checked that in by
mistake. Good that you figur
Om, why did you change the path to download_dependencies.js in the js-swf
package.json? Changing it back gets the script to run for me on Mac. I then
discovered that the download script only downloads the Windows AIR SDK so I'm
currently trying to have it get the DMG for Mac before trying it o
I think I got it working...
On 9/10/19, 5:18 PM, "OmPrakash Muppirala" wrote:
Damn I dint know about that. I would be okay doing it manually this time
and fixing the scripts for next release
Unless Alex, you want to power through it this time.
Om
On Tue, Sep 10, 2
Damn I dint know about that. I would be okay doing it manually this time
and fixing the scripts for next release
Unless Alex, you want to power through it this time.
Om
On Tue, Sep 10, 2019 at 4:53 PM Alex Harui wrote:
> I was going to try to publish another test package, but the npm/publish.j
I was going to try to publish another test package, but the npm/publish.js
script is not working for me. Om, did you use it? It appears that npm has
removed the registry API and we are supposed to use an
npm-publish-programmatically module instead?
I may play with that today, so if you see mo
Hi,
I'm all for homebrew in Mac, when I have time and reinstall it to avoid
sudo, I'll do with homebrew for sure. I have all installed that way.
El mar., 10 sept. 2019 a las 7:26, Alex Harui ()
escribió:
> I tried to remove node and npm and re-install it without sudo via homebrew.
>
> I think I
Hi Om,
result for that console command is:
macbookpro:royale-compiler carlosrovira$ ls $(npm prefix
-g)/lib/node_modules
*@apache-royale* *asconfigc* *npm*
Thanks
Carlos
El lun., 9 sept. 2019 a las 23:16, OmPrakash Muppirala (<
bigosma...@gmail.com>) escribió:
> Carlos,
>
> Sorry, I was
I tried to remove node and npm and re-install it without sudo via homebrew.
I think I got the same results as Carlos. FWIW, there is no @apache_royale
folder in node_modules.
~$ npm i @apache-royale/royale-js-swf@0.9.6-beta0 -g
/usr/local/bin/asjscompc ->
/usr/local/lib/node_modules/@apache-ro
Carlos,
Sorry, I was not clear.
We run the dependencies.js script after the installation as a `postInstall`
script. It assumes that the @apache-royale/royale-js-swf directory is
created inside your global npm node_module directories.
You can verify if the package installed correctly in the first
Hi Om,
this is just a path you asked me for "dependencies.js" file, not the
command line. The command line is already in the error log above this
thread. There's something like this:
macbookpro:~ carlosrovira$ npm i @apache-royale/royale-js-swf@0.9.6-beta0 -g
best
C.
El lun., 9 sept. 2019 a l
Huh? Did you use the - g switch? Your path indicates that you probably
did not..
On Mon, Sep 9, 2019, 7:10 AM Carlos Rovira wrote:
> Hi Om,
>
> the path is: "*/npm/js-swf/dependencies/*"
>
> HTH
> Carlos
>
> El vie., 6 sept. 2019 a las 19:41, OmPrakash Muppirala (<
> bigosma...@gmail.com>) esc
Hi Om,
the path is: "*/npm/js-swf/dependencies/*"
HTH
Carlos
El vie., 6 sept. 2019 a las 19:41, OmPrakash Muppirala (<
bigosma...@gmail.com>) escribió:
> Thanks Carlos, this is useful!
>
> Can you send the path for the dependencies.js file you have shown here?
>
> Regards,
> Om
>
> On Fri, Sep
Thanks Carlos, this is useful!
Can you send the path for the dependencies.js file you have shown here?
Regards,
Om
On Fri, Sep 6, 2019 at 12:42 AM Carlos Rovira
wrote:
> Hi,
>
> I'll try to see Om links as I have time. In the mean while here is the log:
>
> https://paste.apache.org/p/pomzf
>
>
Hi,
I'll try to see Om links as I have time. In the mean while here is the log:
https://paste.apache.org/p/pomzf
and dependencies.js
https://paste.apache.org/p/6nu70
HTH
Carlos
El jue., 5 sept. 2019 a las 18:32, OmPrakash Muppirala (<
bigosma...@apache.org>) escribió:
> If you have to
If you have to use sudo that usually means that your node/npm is not setup
correctly.
Some more info here :
https://medium.com/@ExplosionPills/dont-use-sudo-with-npm-still-66e609f5f92
https://stackoverflow.com/a/18296178
That said, this issue is not related to sudo or otherwise.
But it is a goo
Pretty sure if you use -g on MacOS you need sudo. However, I don't think
that's the issue here.
I think Carlos should post his:
- dependencies/download_dependencies.js`
- /Users/carlosrovira/.npm/_logs/2019-09-05T09_39_50_359Z-debug.log
HTH,
-Alex
On 9/5/19, 7:28 AM, "OmPrakash Muppirala" wro
Hi Om:
node -v -> v10.12.0
npm -v. -> 6.11.2
thanks!
El jue., 5 sept. 2019 a las 16:28, OmPrakash Muppirala (<
bigosma...@gmail.com>) escribió:
> And oh, what is your node version?
>
> On Thu, Sep 5, 2019, 7:27 AM OmPrakash Muppirala
> wrote:
>
> > We should never have to install any npm pack
And oh, what is your node version?
On Thu, Sep 5, 2019, 7:27 AM OmPrakash Muppirala
wrote:
> We should never have to install any npm package with sudo.
>
> I will dig deeper into this and see what I can do.
>
> Thanks for testing!
>
> Om
>
>
> On Thu, Sep 5, 2019, 2:41 AM Carlos Rovira
> wrote:
We should never have to install any npm package with sudo.
I will dig deeper into this and see what I can do.
Thanks for testing!
Om
On Thu, Sep 5, 2019, 2:41 AM Carlos Rovira wrote:
> Thanks Harbs,
> that seems not to fix the problem:
>
> macbookpro:~ carlosrovira$ sudo npm i
> @apache-roya
Thanks Harbs,
that seems not to fix the problem:
macbookpro:~ carlosrovira$ sudo npm i
@apache-royale/royale-js-swf@0.9.6-beta0 -g
Password:
/usr/local/bin/asjsc ->
/usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscnpm
/usr/local/bin/asjscompc ->
/usr/local/lib/no
Try sudo.
> On Sep 5, 2019, at 12:24 PM, Carlos Rovira wrote:
>
> Hi Om,
>
> I tried to install now with : npm i @apache-royale/royale-js-swf@0.9.6-beta0
> -g
>
> I get this:
>
> Last login: Fri Aug 30 00:01:50 on ttys000
>
> macbookpro:~ carlosrovira$ npm i @apache-royale/royale-js-swf@0.9.
Hi Om,
I tried to install now with : npm i @apache-royale/royale-js-swf@0.9.6-beta0
-g
I get this:
Last login: Fri Aug 30 00:01:50 on ttys000
macbookpro:~ carlosrovira$ npm i @apache-royale/royale-js-swf@0.9.6-beta0 -g
/usr/local/bin/asjsc ->
/usr/local/lib/node_modules/@apache-royale/royale-j
Carlos,
A nice way to test if your installation is working correctly is to try it
with the npm cli tool.
You can install the cli using the command:
npm i @apache-royale/cli -g
Basically install the royale package, then install the cli package. And
follow the instructions here:
https://www.npmj
Hi Om,
since I don't know too much about NPM, I want to know some few things about
the Royale NPM version. Just uninstalled old version successfully.
Now, I'm on Mac. if I install the new one, how this affects my environment?
I suppose that my installation of repos to build from source code is
in
Hi folks,
Can you please test the beta release and report any errors you are seeing?
You can test it with these commands:
npm uninstall @apache-royale/royale-js-swf -g (in case you already have it
installed)
npm i @apache-royale/royale-js-swf@0.9.6-beta0 -g
Thanks,
Om
On Sun, Sep 1, 2019 at 7:
Just a heads up, I will be doing some test publishes of the royale npm
package. I will be using the version number: 0.9.6.beta.1 (0.9.6.beta.2,
etc if needed)
These fixes are related to these tickets:
https://github.com/apache/royale-asjs/issues/428
https://github.com/apache/royale-asjs/issues/4
28 matches
Mail list logo