Re: Royale CLI issues

[Dany Dhondt]

Hi Om

I uninstalled royale-js and cli
the first gave the same 'invalid entry' errors but installed anyway

the cli gave these errors (I did install with sudo!):


node-pre-gyp ERR! Pre-built binaries not installable for fsevents@1.2.3 and 
node@10.0.0 (node-v64 ABI, unknown) (falling back to source compile with 
node-gyp) 
node-pre-gyp ERR! Hit error EACCES: permission denied, mkdir 
'/usr/local/lib/node_modules/@apache-royale/cli/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64'
 
gyp ERR! clean error 
gyp ERR! stack Error: EACCES: permission denied, rmdir 'build'
gyp ERR! System Darwin 17.5.0
gyp ERR! command "/usr/local/bin/node" 
"/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "clean"
gyp ERR! cwd 
/usr/local/lib/node_modules/@apache-royale/cli/node_modules/fsevents
gyp ERR! node -v v10.0.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node 
/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js clean' (1)
node-pre-gyp ERR! stack     at ChildProcess. 
(/usr/local/lib/node_modules/@apache-royale/cli/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:947:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit 
(internal/child_process.js:236:5)
node-pre-gyp ERR! System Darwin 17.5.0
node-pre-gyp ERR! command "/usr/local/bin/node" 
"/usr/local/lib/node_modules/@apache-royale/cli/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp"
 "install" "--fallback-to-build"
node-pre-gyp ERR! cwd 
/usr/local/lib/node_modules/@apache-royale/cli/node_modules/fsevents
node-pre-gyp ERR! node -v v10.0.0
node-pre-gyp ERR! node-pre-gyp -v v0.9.1
node-pre-gyp ERR! not ok 
Failed to execute '/usr/local/bin/node 
/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js clean' (1)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.3 
(node_modules/@apache-royale/cli/node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.3 install: `node 
install`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1




Thoughts?

Dany

Op 8 mei 2018 om 08:40 uur uur schreef OmPrakash Muppirala 
:

Dany,

I updated my pushed a new version of cli a couple days ago. This was
published using the latest versions of npm and node.js

Can you please try these commands and let me know how it goes?

npm install -g @apache-royale/royale-js
npm install -g @apache-royale/cli

royale new new-test
cd new-test
royale serve:debug



Thanks,
Om

On Wed, May 2, 2018 at 1:05 AM, Dany Dhondt  wrote:

:) nice to know that messing things up makes your day

My aim is to expand the Hello world app to a real boilerplate app in which
a basic layout is used and where most common components are shown.
I would also like to implement one server call (which might return some
json) to get people started.

-Dany

Op 2 mei 2018 om 09:59 uur uur schreef OmPrakash Muppirala <
bigosma...@gmail.com>:

Okay, I bumped my versions and the good news is that everything is messed
up on my computer as well :-)

Thanks for your patience Dany. I will try to debug this issue soon and
make a new release.

Regards,
Om

On Wed, May 2, 2018 at 12:23 AM, Dany Dhondt  wrote:

my-royale-app dany$ > node -v


v8.11.1


my-royale-app dany$ > npm -v


6.0.0



-Dany



Op 2 mei 2018 om 09:19 uur uur schreef OmPrakash Muppirala <

bigosma...@gmail.com>:


Ah that makes more sense. It looks like mxmlc (the compiler) is not able

to access the Main.mxml file. So, it fails at the compilation step.

Instead of erroring out right away, the server tries to load a non existent

index.html.


As someone mentioned earlier, this might be because of the npm version

mismatch.

Can you please let me know what your npm and node.js versions are?


Mine are:

C:\temp\royale-test\my-app>npm -v

4.3.0


C:\temp\royale-test\my-app>node -v

v7.7.1


Thanks,

Om


On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt  wrote:


this is the complete error listing:



my-royale-app dany$ > royale serve:debug



Compiling...



WARNING: An illegal reflective access operation has occurred



WARNING: Illegal reflective access by com.google.common.base.

internal.Finalizer


(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/

royale-asjs/js/lib/guava.jar)


to field java.lang.Thread.inheritableThreadLocals



WARNING: Please consider reporting this to the maintainers of


com.google.common.base.internal.Finalizer



WARNING: Use --illegal-access=warn to enable warnings of further illegal


reflective access operations



WARNING: All illegal access operations will be denied in a future release



Error: unable to open 'HD/Documents/ARCHEMEDIA/

Re: Royale CLI issues

[OmPrakash Muppirala]

Dany,

I updated my pushed a new version of cli a couple days ago.  This was
published using the latest versions of npm and node.js

Can you please try these commands and let me know how it goes?

npm install -g @apache-royale/royale-js
npm install -g @apache-royale/cli

royale new new-test
cd new-test
royale serve:debug



Thanks,
Om

On Wed, May 2, 2018 at 1:05 AM, Dany Dhondt  wrote:

> :) nice to know that messing things up makes your day
>
> My aim is to expand the Hello world app to a real boilerplate app in which
> a basic layout is used and where most common components are shown.
> I would also like to implement one server call (which might return some
> json) to get people started.
>
> -Dany
>
> Op 2 mei 2018 om 09:59 uur uur schreef OmPrakash Muppirala <
> bigosma...@gmail.com>:
>
> Okay, I bumped my versions and the good news is that everything is messed
> up on my computer as well :-)
>
> Thanks for your patience Dany. I will try to debug this issue soon and
> make a new release.
>
> Regards,
> Om
>
> On Wed, May 2, 2018 at 12:23 AM, Dany Dhondt  wrote:
>
> my-royale-app dany$ > node -v
>
>
> v8.11.1
>
>
> my-royale-app dany$ > npm -v
>
>
> 6.0.0
>
>
>
> -Dany
>
>
>
> Op 2 mei 2018 om 09:19 uur uur schreef OmPrakash Muppirala <
>
> bigosma...@gmail.com>:
>
>
> Ah that makes more sense. It looks like mxmlc (the compiler) is not able
>
> to access the Main.mxml file. So, it fails at the compilation step.
>
> Instead of erroring out right away, the server tries to load a non existent
>
> index.html.
>
>
> As someone mentioned earlier, this might be because of the npm version
>
> mismatch.
>
> Can you please let me know what your npm and node.js versions are?
>
>
> Mine are:
>
> C:\temp\royale-test\my-app>npm -v
>
> 4.3.0
>
>
> C:\temp\royale-test\my-app>node -v
>
> v7.7.1
>
>
> Thanks,
>
> Om
>
>
> On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt  wrote:
>
>
> this is the complete error listing:
>
>
>
> my-royale-app dany$ > royale serve:debug
>
>
>
> Compiling...
>
>
>
> WARNING: An illegal reflective access operation has occurred
>
>
>
> WARNING: Illegal reflective access by com.google.common.base.
>
> internal.Finalizer
>
>
> (file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/
>
> royale-asjs/js/lib/guava.jar)
>
>
> to field java.lang.Thread.inheritableThreadLocals
>
>
>
> WARNING: Please consider reporting this to the maintainers of
>
>
> com.google.common.base.internal.Finalizer
>
>
>
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>
>
> reflective access operations
>
>
>
> WARNING: All illegal access operations will be denied in a future release
>
>
>
> Error: unable to open 'HD/Documents/ARCHEMEDIA/
>
>
> ROYALE/my-royale-app/src/Main.mxml'.
>
>
>
>
>
>
> Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
>
>
> ROYALE/my-royale-app/src/Main.mxml -debug=true
>
>
>
> WARNING: An illegal reflective access operation has occurred
>
>
>
> WARNING: Illegal reflective access by com.google.common.base.
>
> internal.Finalizer
>
>
> (file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/
>
> royale-asjs/js/lib/guava.jar)
>
>
> to field java.lang.Thread.inheritableThreadLocals
>
>
>
> WARNING: Please consider reporting this to the maintainers of
>
>
> com.google.common.base.internal.Finalizer
>
>
>
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>
>
> reflective access operations
>
>
>
> WARNING: All illegal access operations will be denied in a future release
>
>
>
> Error: unable to open 'HD/Documents/ARCHEMEDIA/
>
>
> ROYALE/my-royale-app/src/Main.mxml'.
>
>
>
>
>
>
>
> fs.js:646
>
>
>
> return binding.open(pathModule._makeLong(path), stringToFlags(flags),
>
>
> mode);
>
>
>
> ^
>
>
>
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
>
>
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
>
>
>
> at Object.fs.openSync (fs.js:646:18)
>
>
>
> at Object.fs.readFileSync (fs.js:551:33)
>
>
>
> at updateIndex (/usr/local/lib/node_modules/@
>
>
> apache-royale/cli/index.js:125:24)
>
>
>
> at compileDebug (/usr/local/lib/node_modules/@
>
>
> apache-royale/cli/index.js:106:9)
>
>
>
> at serveDebug (/usr/local/lib/node_modules/@
>
>
> apache-royale/cli/index.js:88:5)
>
>
>
> at Object. (/usr/local/lib/node_modules/@
>
>
> apache-royale/cli/index.js:59:13)
>
>
>
> at Module._compile (module.js:652:30)
>
>
>
> at Object.Module._extensions..js (module.js:663:10)
>
>
>
> at Module.load (module.js:565:32)
>
>
>
> at tryModuleLoad (module.js:505:12)
>
>
>
>
>
>
>
>
>
>

Re: Royale CLI issues

[Dany Dhondt]

:) nice to know that messing things up makes your day

My aim is to expand the Hello world app to a real boilerplate app in which a 
basic layout is used and where most common components are shown. 
I would also like to implement one server call (which might return some json) 
to get people started.

-Dany

Op 2 mei 2018 om 09:59 uur uur schreef OmPrakash Muppirala 
:

Okay, I bumped my versions and the good news is that everything is messed
up on my computer as well :-)

Thanks for your patience Dany. I will try to debug this issue soon and
make a new release.

Regards,
Om

On Wed, May 2, 2018 at 12:23 AM, Dany Dhondt  wrote:

my-royale-app dany$ > node -v

v8.11.1

my-royale-app dany$ > npm -v

6.0.0


-Dany


Op 2 mei 2018 om 09:19 uur uur schreef OmPrakash Muppirala <
bigosma...@gmail.com>:

Ah that makes more sense. It looks like mxmlc (the compiler) is not able
to access the Main.mxml file. So, it fails at the compilation step.
Instead of erroring out right away, the server tries to load a non existent
index.html.

As someone mentioned earlier, this might be because of the npm version
mismatch.
Can you please let me know what your npm and node.js versions are?

Mine are:
C:\temp\royale-test\my-app>npm -v
4.3.0

C:\temp\royale-test\my-app>node -v
v7.7.1

Thanks,
Om

On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt  wrote:

this is the complete error listing:


my-royale-app dany$ > royale serve:debug


Compiling...


WARNING: An illegal reflective access operation has occurred


WARNING: Illegal reflective access by com.google.common.base.
internal.Finalizer

(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/
royale-asjs/js/lib/guava.jar)

to field java.lang.Thread.inheritableThreadLocals


WARNING: Please consider reporting this to the maintainers of

com.google.common.base.internal.Finalizer


WARNING: Use --illegal-access=warn to enable warnings of further illegal

reflective access operations


WARNING: All illegal access operations will be denied in a future release


Error: unable to open 'HD/Documents/ARCHEMEDIA/

ROYALE/my-royale-app/src/Main.mxml'.





Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/

ROYALE/my-royale-app/src/Main.mxml -debug=true


WARNING: An illegal reflective access operation has occurred


WARNING: Illegal reflective access by com.google.common.base.
internal.Finalizer

(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/
royale-asjs/js/lib/guava.jar)

to field java.lang.Thread.inheritableThreadLocals


WARNING: Please consider reporting this to the maintainers of

com.google.common.base.internal.Finalizer


WARNING: Use --illegal-access=warn to enable warnings of further illegal

reflective access operations


WARNING: All illegal access operations will be denied in a future release


Error: unable to open 'HD/Documents/ARCHEMEDIA/

ROYALE/my-royale-app/src/Main.mxml'.






fs.js:646


return binding.open(pathModule._makeLong(path), stringToFlags(flags),

mode);


^



Error: ENOENT: no such file or directory, open '/Volumes/Macintosh

HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'


at Object.fs.openSync (fs.js:646:18)


at Object.fs.readFileSync (fs.js:551:33)


at updateIndex (/usr/local/lib/node_modules/@

apache-royale/cli/index.js:125:24)


at compileDebug (/usr/local/lib/node_modules/@

apache-royale/cli/index.js:106:9)


at serveDebug (/usr/local/lib/node_modules/@

apache-royale/cli/index.js:88:5)


at Object. (/usr/local/lib/node_modules/@

apache-royale/cli/index.js:59:13)


at Module._compile (module.js:652:30)


at Object.Module._extensions..js (module.js:663:10)


at Module.load (module.js:565:32)


at tryModuleLoad (module.js:505:12)

Re: Royale CLI issues

[Dany Dhondt]

my-royale-app dany$  > node -v
v8.11.1
my-royale-app dany$  > npm -v
6.0.0


-Dany


Op 2 mei 2018 om 09:19 uur uur schreef OmPrakash Muppirala 
:

Ah that makes more sense. It looks like mxmlc (the compiler) is not able
to access the Main.mxml file. So, it fails at the compilation step.
Instead of erroring out right away, the server tries to load a non existent
index.html.

As someone mentioned earlier, this might be because of the npm version
mismatch.
Can you please let me know what your npm and node.js versions are?

Mine are:
C:\temp\royale-test\my-app>npm -v
4.3.0

C:\temp\royale-test\my-app>node -v
v7.7.1

Thanks,
Om

On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt  wrote:

this is the complete error listing:

my-royale-app dany$ > royale serve:debug

Compiling...

WARNING: An illegal reflective access operation has occurred

WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer
(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
to field java.lang.Thread.inheritableThreadLocals

WARNING: Please consider reporting this to the maintainers of
com.google.common.base.internal.Finalizer

WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations

WARNING: All illegal access operations will be denied in a future release

Error: unable to open 'HD/Documents/ARCHEMEDIA/
ROYALE/my-royale-app/src/Main.mxml'.




Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
ROYALE/my-royale-app/src/Main.mxml -debug=true

WARNING: An illegal reflective access operation has occurred

WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer
(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
to field java.lang.Thread.inheritableThreadLocals

WARNING: Please consider reporting this to the maintainers of
com.google.common.base.internal.Finalizer

WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations

WARNING: All illegal access operations will be denied in a future release

Error: unable to open 'HD/Documents/ARCHEMEDIA/
ROYALE/my-royale-app/src/Main.mxml'.





fs.js:646

return binding.open(pathModule._makeLong(path), stringToFlags(flags),
mode);

^


Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'

at Object.fs.openSync (fs.js:646:18)

at Object.fs.readFileSync (fs.js:551:33)

at updateIndex (/usr/local/lib/node_modules/@
apache-royale/cli/index.js:125:24)

at compileDebug (/usr/local/lib/node_modules/@
apache-royale/cli/index.js:106:9)

at serveDebug (/usr/local/lib/node_modules/@
apache-royale/cli/index.js:88:5)

at Object. (/usr/local/lib/node_modules/@
apache-royale/cli/index.js:59:13)

at Module._compile (module.js:652:30)

at Object.Module._extensions..js (module.js:663:10)

at Module.load (module.js:565:32)

at tryModuleLoad (module.js:505:12)

Re: Royale CLI issues

[OmPrakash Muppirala]

Ah that makes more sense.  It looks like mxmlc (the compiler) is not able
to access the Main.mxml file.  So, it fails at the compilation step.
Instead of erroring out right away, the server tries to load a non existent
index.html.

As someone mentioned earlier, this might be because of the npm version
mismatch.
Can you please let me know what your npm and node.js versions are?

Mine are:
C:\temp\royale-test\my-app>npm -v
4.3.0

C:\temp\royale-test\my-app>node -v
v7.7.1

Thanks,
Om

On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt  wrote:

> this is the complete error listing:
>
> my-royale-app dany$  > royale serve:debug
>
> Compiling...
>
> WARNING: An illegal reflective access operation has occurred
>
> WARNING: Illegal reflective access by 
> com.google.common.base.internal.Finalizer
> (file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
> to field java.lang.Thread.inheritableThreadLocals
>
> WARNING: Please consider reporting this to the maintainers of
> com.google.common.base.internal.Finalizer
>
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
>
> WARNING: All illegal access operations will be denied in a future release
>
> Error: unable to open 'HD/Documents/ARCHEMEDIA/
> ROYALE/my-royale-app/src/Main.mxml'.
>
>
>
>
> Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
> ROYALE/my-royale-app/src/Main.mxml -debug=true
>
> WARNING: An illegal reflective access operation has occurred
>
> WARNING: Illegal reflective access by 
> com.google.common.base.internal.Finalizer
> (file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
> to field java.lang.Thread.inheritableThreadLocals
>
> WARNING: Please consider reporting this to the maintainers of
> com.google.common.base.internal.Finalizer
>
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
>
> WARNING: All illegal access operations will be denied in a future release
>
> Error: unable to open 'HD/Documents/ARCHEMEDIA/
> ROYALE/my-royale-app/src/Main.mxml'.
>
>
>
>
>
> fs.js:646
>
>   return binding.open(pathModule._makeLong(path), stringToFlags(flags),
> mode);
>
>  ^
>
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
>
> at Object.fs.openSync (fs.js:646:18)
>
> at Object.fs.readFileSync (fs.js:551:33)
>
> at updateIndex (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:125:24)
>
> at compileDebug (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:106:9)
>
> at serveDebug (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:88:5)
>
> at Object. (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:59:13)
>
> at Module._compile (module.js:652:30)
>
> at Object.Module._extensions..js (module.js:663:10)
>
> at Module.load (module.js:565:32)
>
> at tryModuleLoad (module.js:505:12)
>
>
>
>
>
>

Re: Royale CLI issues

[Dany Dhondt]

this is the complete error listing:

my-royale-app dany$  > royale serve:debug
Compiling...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer 
(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
 to field java.lang.Thread.inheritableThreadLocals
WARNING: Please consider reporting this to the maintainers of 
com.google.common.base.internal.Finalizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Error: unable to open 
'HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/Main.mxml'.



Command failed: mxmlc /Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/Main.mxml -debug=true
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer 
(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
 to field java.lang.Thread.inheritableThreadLocals
WARNING: Please consider reporting this to the maintainers of 
com.google.common.base.internal.Finalizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Error: unable to open 
'HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/Main.mxml'.




fs.js:646
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
    at Object.fs.openSync (fs.js:646:18)
    at Object.fs.readFileSync (fs.js:551:33)
    at updateIndex 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:125:24)
    at compileDebug 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:106:9)
    at serveDebug (/usr/local/lib/node_modules/@apache-royale/cli/index.js:88:5)
    at Object. 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:59:13)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)

Re: Royale CLI issues

[OmPrakash Muppirala]

On Tue, May 1, 2018 at 11:59 PM, Harbs  wrote:

> The bin folder is created by the compiler while compiling the app. I have
> not been following this discussion very closely. What are you using to
> compile?
>

Please follow the steps here:
https://github.com/apache/royale-asjs/tree/develop/npm/cli to reproduce the
issue.

Thanks,
Om


>
> > On May 2, 2018, at 9:48 AM, Dany Dhondt  wrote:
> >
> > Hi Om,
> >
> > I tried both ways, none of them works.
> > Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
> >
> >
> >
> > My question is: shouldn't the 'new' command create more than just one
> mxml file?
> > What script is responsible for creating the bin folder? Should it be the
> 'new' script or the 'serve' script?
> >
> > -Dany
> >
> >
> > Op 2 mei 2018 om 08:36 uur uur schreef OmPrakash Muppirala <
> bigosma...@gmail.com>:
> >
> >> On Tue, May 1, 2018 at 11:15 PM, Dany Dhondt 
> wrote:
> >>
> >>> Alex,
> >>>
> >>> The version number here came from package.json so it should have been
> >>> updated by someone.
> >>>
> >>> I reinstalled from the link you provided with no problem.
> >>> But running the royale server:debug [1] command gives me the same
> errors
> >>> as before.
> >>>
> >>> I noticed that when running: royale new my-royale-app, only an app
> folder
> >>> is created with a src folder in it.In this src folder, there is a
> main.mxml
> >>> file. So no other files or folders whatsoever are created by the 'new'
> >>> command.
> >>>
> >>
> >> Yes, that is the expected behavior. Currently, we ship a very simple
> >> `Hello World` app with the royale-cli tool. We can make it fancier app
> >> once we iron out all the issues.
> >>
> >>
> >>>
> >>> This explains the error:
> >>>
> >>> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> >>> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/
> js-debug/index.html'
> >>>
> >>>
> >> Hmm, the path does not seem correct. it should be
> >> .../my-royale-app/bin/js-debug/index.html instead of what is shown
> here.
> >>
> >> It appears that you are running the royale serve:debug command from the
> >> .../my-royale-app/src directory instead of from the .../my-royale-app
> >> directory.
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>> -Dany
> >>>
> >>> [1] https://github.com/apache/royale-asjs/tree/develop/npm/cli <
> https://github.com/apache/royale-asjs/tree/develop/npm/cli>
> >>> Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui
>  >>> >:
> >>>
> >>> That's my windows machine that I used for 0.9.2.
> >>>
> >>> Where did it say 0.9.3? I'm trying to remember if I published the
> package
> >>> to NPM or if you did. Maybe the scripts are running or were run after
> some
> >>> versions got updated in the repos. I have not run a build on my windows
> >>> machine since the release.
> >>>
> >>> -Alex
> >>>
> >>> On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala" <
> >>> omup...@gmail.com  on behalf of
> bigosma...@gmail.com > wrote:
> >>>
> >>> On Tue, May 1, 2018 at 1:36 PM, Alex Harui 
> >>> wrote:
> >>>
> >>> > Om,
> >>> >
> >>> > I got the warnings when we released 0.9.2 but it appeared to leave a
> >>> > functional SDK. Now it is hanging for me and Dany.
> >>> >
> >>> > I don't think I've run a publish and I don't think the CI server is
> >>> > either, but you never know. Try grabbing one of the SWCs. Unzip it
> and
> >>> > swfdump the library.swf. There should be debugfile bytecodes with
> paths
> >>> to
> >>> > the source that give us a clue.
> >>> >
> >>> >
> >>> Good idea. Here is what I see in swfdump:
> >>>
> >>> 2) + 0:1 debugfile
> >>> "C:\temp\rc\royale-asjs\frameworks\projects\
> Collections\src\main\royale;
> >>> org\apache\royale\collections;FlattenedList.as"
> >>>
> >>> Any idea whose machine this could have been?
> >>>
> >>> Thanks,
> >>> Om
> >>>
> >>>
> >>> > -Alex
> >>> >
> >>> > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> >>> > Muppirala"  > wrote:
> >>> >
> >>> > On Tue, May 1, 2018 at 8:57 AM, Alex Harui  >
> >>> > wrote:
> >>> >
> >>> > > Hi Dany,
> >>> > >
> >>> > > The link is directly to a tar.gz built by our CI server. No humans
> >>> > > involved, and no special packaging for NPM. NPM says it can install
> >>> > any
> >>> > > tar.gz file. Try downloading the file at that link and using Mac
> >>> > Finder to
> >>> > > expand it into a folder. For me it expands without errors. This is
> >>> > why I
> >>> > > believe it is some incompatibility with NPM.
> >>> > >
> >>> > > If the tar.gz expands for you on Mac, you can try to "npm install"
> >>> > the
> >>> > > folder. Running:
> >>> > >
> >>> > > sudo npm install -g 
> 

Re: Royale CLI issues

[Harbs]

The bin folder is created by the compiler while compiling the app. I have not 
been following this discussion very closely. What are you using to compile?

> On May 2, 2018, at 9:48 AM, Dany Dhondt  wrote:
> 
> Hi Om,
> 
> I tried both ways, none of them works.
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh 
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
>
> 
> 
> My question is: shouldn't the 'new' command create more than just one mxml 
> file?
> What script is responsible for creating the bin folder? Should it be the 
> 'new' script or the 'serve' script?
> 
> -Dany
> 
> 
> Op 2 mei 2018 om 08:36 uur uur schreef OmPrakash Muppirala 
> :
> 
>> On Tue, May 1, 2018 at 11:15 PM, Dany Dhondt  wrote:
>> 
>>> Alex,
>>> 
>>> The version number here came from package.json so it should have been
>>> updated by someone.
>>> 
>>> I reinstalled from the link you provided with no problem.
>>> But running the royale server:debug [1] command gives me the same errors
>>> as before.
>>> 
>>> I noticed that when running: royale new my-royale-app, only an app folder
>>> is created with a src folder in it.In this src folder, there is a main.mxml
>>> file. So no other files or folders whatsoever are created by the 'new'
>>> command.
>>> 
>> 
>> Yes, that is the expected behavior. Currently, we ship a very simple
>> `Hello World` app with the royale-cli tool. We can make it fancier app
>> once we iron out all the issues.
>> 
>> 
>>> 
>>> This explains the error:
>>> 
>>> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
>>> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/js-debug/index.html'
>>> 
>>> 
>> Hmm, the path does not seem correct. it should be
>> .../my-royale-app/bin/js-debug/index.html instead of what is shown here.
>> 
>> It appears that you are running the royale serve:debug command from the
>> .../my-royale-app/src directory instead of from the .../my-royale-app
>> directory.
>> 
>> Thanks,
>> Om
>> 
>> 
>>> -Dany
>>> 
>>> [1] https://github.com/apache/royale-asjs/tree/develop/npm/cli 
>>> 
>>> Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui >> >:
>>> 
>>> That's my windows machine that I used for 0.9.2.
>>> 
>>> Where did it say 0.9.3? I'm trying to remember if I published the package
>>> to NPM or if you did. Maybe the scripts are running or were run after some
>>> versions got updated in the repos. I have not run a build on my windows
>>> machine since the release.
>>> 
>>> -Alex
>>> 
>>> On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <
>>> omup...@gmail.com  on behalf of 
>>> bigosma...@gmail.com > wrote:
>>> 
>>> On Tue, May 1, 2018 at 1:36 PM, Alex Harui 
>>> wrote:
>>> 
>>> > Om,
>>> >
>>> > I got the warnings when we released 0.9.2 but it appeared to leave a
>>> > functional SDK. Now it is hanging for me and Dany.
>>> >
>>> > I don't think I've run a publish and I don't think the CI server is
>>> > either, but you never know. Try grabbing one of the SWCs. Unzip it and
>>> > swfdump the library.swf. There should be debugfile bytecodes with paths
>>> to
>>> > the source that give us a clue.
>>> >
>>> >
>>> Good idea. Here is what I see in swfdump:
>>> 
>>> 2) + 0:1 debugfile
>>> "C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;
>>> org\apache\royale\collections;FlattenedList.as"
>>> 
>>> Any idea whose machine this could have been?
>>> 
>>> Thanks,
>>> Om
>>> 
>>> 
>>> > -Alex
>>> >
>>> > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
>>> > Muppirala" >> > > wrote:
>>> >
>>> > On Tue, May 1, 2018 at 8:57 AM, Alex Harui 
>>> > wrote:
>>> >
>>> > > Hi Dany,
>>> > >
>>> > > The link is directly to a tar.gz built by our CI server. No humans
>>> > > involved, and no special packaging for NPM. NPM says it can install
>>> > any
>>> > > tar.gz file. Try downloading the file at that link and using Mac
>>> > Finder to
>>> > > expand it into a folder. For me it expands without errors. This is
>>> > why I
>>> > > believe it is some incompatibility with NPM.
>>> > >
>>> > > If the tar.gz expands for you on Mac, you can try to "npm install"
>>> > the
>>> > > folder. Running:
>>> > >
>>> > > sudo npm install -g 
>>> > >
>>> > > seemed to work for me.
>>> > >
>>> > > -Alex
>>> > >
>>> >
>>> > I just tried
>>> > npm install @apache-royale/royale-js -g
>>> > on windwos and it installed just fine.
>>> >
>>> > Although, I notice that @apache-royale/royale-js@0.9.3 was
>>> > installed. It
>>> > should have installed 0.9.2. Did we publish 0.9.3 to npm by mistake?
>>> > Could that be related?
>>> >
>>> > Thanks,
>>> > Om
>>> >
>>> >
>>> > >
>>> > > On 

Re: Royale CLI issues

[OmPrakash Muppirala]

On Tue, May 1, 2018 at 11:48 PM, Dany Dhondt  wrote:

> Hi Om,
>
> I tried both ways, none of them works.
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
>
>
>
>
>
>
Can I see the entire content of your terminal when you run these commands?


> My question is: shouldn't the 'new' command create more than just one mxml
> file?
> What script is responsible for creating the bin folder? Should it be the
> 'new' script or the 'serve' script?
>

The `royale new` command just copies a template directory (which contains
only one mxml file) into the my-royale-app/src directory.
The `royale serve:debug` command does the following:


   - Compiles the project in debug mode
   - Compiles with source map option
   - Starts a http server and serves the files from the bin/js-debug
   directory
   - Opens the default browser and navigates to http://localhost:3000
   - Listens to src folder
   - When any file changes, it will recompile the app
   - Automatically reloads the browser to show the updated application


All the logic is in here:
https://github.com/apache/royale-asjs/blob/develop/npm/cli/index.js

Thanks,
Om


> -Dany
>
>
> Op 2 mei 2018 om 08:36 uur uur schreef OmPrakash Muppirala <
> bigosma...@gmail.com>:
>
> On Tue, May 1, 2018 at 11:15 PM, Dany Dhondt  wrote:
>
> Alex,
>
>
> The version number here came from package.json so it should have been
>
> updated by someone.
>
>
> I reinstalled from the link you provided with no problem.
>
> But running the royale server:debug [1] command gives me the same errors
>
> as before.
>
>
> I noticed that when running: royale new my-royale-app, only an app folder
>
> is created with a src folder in it.In this src folder, there is a main.mxml
>
> file. So no other files or folders whatsoever are created by the 'new'
>
> command.
>
>
>
> Yes, that is the expected behavior. Currently, we ship a very simple
> `Hello World` app with the royale-cli tool. We can make it fancier app
> once we iron out all the issues.
>
>
>
> This explains the error:
>
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
>
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/js-debug/index.html'
>
>
>
> Hmm, the path does not seem correct. it should be
> .../my-royale-app/bin/js-debug/index.html instead of what is shown here.
>
> It appears that you are running the royale serve:debug command from the
> .../my-royale-app/src directory instead of from the .../my-royale-app
> directory.
>
> Thanks,
> Om
>
>
> -Dany
>
>
> [1] https://github.com/apache/royale-asjs/tree/develop/npm/cli
>
>
> Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui 
> >:
>
>
> That's my windows machine that I used for 0.9.2.
>
>
> Where did it say 0.9.3? I'm trying to remember if I published the package
>
> to NPM or if you did. Maybe the scripts are running or were run after some
>
> versions got updated in the repos. I have not run a build on my windows
>
> machine since the release.
>
>
> -Alex
>
>
> On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <
>
> omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>
>
> On Tue, May 1, 2018 at 1:36 PM, Alex Harui 
>
> wrote:
>
>
> > Om,
>
> >
>
> > I got the warnings when we released 0.9.2 but it appeared to leave a
>
> > functional SDK. Now it is hanging for me and Dany.
>
> >
>
> > I don't think I've run a publish and I don't think the CI server is
>
> > either, but you never know. Try grabbing one of the SWCs. Unzip it and
>
> > swfdump the library.swf. There should be debugfile bytecodes with paths
>
> to
>
> > the source that give us a clue.
>
> >
>
> >
>
> Good idea. Here is what I see in swfdump:
>
>
> 2) + 0:1 debugfile
>
> "C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;
>
> org\apache\royale\collections;FlattenedList.as"
>
>
> Any idea whose machine this could have been?
>
>
> Thanks,
>
> Om
>
>
>
> > -Alex
>
> >
>
> > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
>
> > Muppirala"  wrote:
>
> >
>
> > On Tue, May 1, 2018 at 8:57 AM, Alex Harui 
>
> > wrote:
>
> >
>
> > > Hi Dany,
>
> > >
>
> > > The link is directly to a tar.gz built by our CI server. No humans
>
> > > involved, and no special packaging for NPM. NPM says it can install
>
> > any
>
> > > tar.gz file. Try downloading the file at that link and using Mac
>
> > Finder to
>
> > > expand it into a folder. For me it expands without errors. This is
>
> > why I
>
> > > believe it is some incompatibility with NPM.
>
> > >
>
> > > If the tar.gz expands for you on Mac, you can try to "npm install"
>
> > the
>
> > > folder. Running:
>
> > >
>
> > > sudo npm install -g 
>
> > >
>
> > > seemed to work for me.
>
> > >
>
> > > -Alex
>
> > >
>
> >
>
> > I just tried
>
> 

Re: Royale CLI issues

[Dany Dhondt]

Hi Om,

I tried both ways, none of them works.
Error: ENOENT: no such file or directory, open '/Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
   


My question is: shouldn't the 'new' command create more than just one mxml file?
What script is responsible for creating the bin folder? Should it be the 'new' 
script or the 'serve' script?

-Dany


Op 2 mei 2018 om 08:36 uur uur schreef OmPrakash Muppirala 
:

On Tue, May 1, 2018 at 11:15 PM, Dany Dhondt  wrote:

Alex,

The version number here came from package.json so it should have been
updated by someone.

I reinstalled from the link you provided with no problem.
But running the royale server:debug [1] command gives me the same errors
as before.

I noticed that when running: royale new my-royale-app, only an app folder
is created with a src folder in it.In this src folder, there is a main.mxml
file. So no other files or folders whatsoever are created by the 'new'
command.


Yes, that is the expected behavior. Currently, we ship a very simple
`Hello World` app with the royale-cli tool. We can make it fancier app
once we iron out all the issues.



This explains the error:

Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/js-debug/index.html'


Hmm, the path does not seem correct. it should be
.../my-royale-app/bin/js-debug/index.html instead of what is shown here.

It appears that you are running the royale serve:debug command from the
.../my-royale-app/src directory instead of from the .../my-royale-app
directory.

Thanks,
Om


-Dany

[1] https://github.com/apache/royale-asjs/tree/develop/npm/cli

Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui  wrote:

On Tue, May 1, 2018 at 1:36 PM, Alex Harui 
wrote:


Om,

I got the warnings when we released 0.9.2 but it appeared to leave a
functional SDK. Now it is hanging for me and Dany.

I don't think I've run a publish and I don't think the CI server is
either, but you never know. Try grabbing one of the SWCs. Unzip it and
swfdump the library.swf. There should be debugfile bytecodes with paths

to

the source that give us a clue.



Good idea. Here is what I see in swfdump:

2) + 0:1 debugfile
"C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;
org\apache\royale\collections;FlattenedList.as"

Any idea whose machine this could have been?

Thanks,
Om



-Alex

On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
Muppirala"  wrote:

On Tue, May 1, 2018 at 8:57 AM, Alex Harui 
wrote:

> Hi Dany,
>
> The link is directly to a tar.gz built by our CI server. No humans
> involved, and no special packaging for NPM. NPM says it can install
any
> tar.gz file. Try downloading the file at that link and using Mac
Finder to
> expand it into a folder. For me it expands without errors. This is
why I
> believe it is some incompatibility with NPM.
>
> If the tar.gz expands for you on Mac, you can try to "npm install"
the
> folder. Running:
>
> sudo npm install -g 
>
> seemed to work for me.
>
> -Alex
>

I just tried
npm install @apache-royale/royale-js -g
on windwos and it installed just fine.

Although, I notice that @apache-royale/royale-js@0.9.3 was
installed. It
should have installed 0.9.2. Did we publish 0.9.3 to npm by mistake?
Could that be related?

Thanks,
Om


>
> On 5/1/18, 1:51 AM, "Dany Dhondt"  wrote:
>
> Hi Alex,
>
> I tried the direct link you provided: same result (hundreds of
> ‘invalid entry’ messages)
>
> My version of npm is 6.0.0
>
> downgrading to a lower npm version is not an option at this
moment
> because I’m on a production mac with crucial projects on it.
>
> Amids all the invalid entry messages, now and then is a somewhat
> longer message like
>
> WARN⸨ ░░░⸩ ⠸ extract:@apache-royale/royale-js:
verb
> lock using /Users/ tar invalid entry
>
>
>
>
> Is it Om that created this package? This might give him an idea
of
> what’s going on?
>
> -Dany
>
>
>
> > Op 30 apr. 2018, om 18:39 heeft Alex Harui
 > het volgende geschreven:
> >
> > Hmm. I'm getting that too on my Mac. It used to complete
anyway
> and work, but now it appears to be hanging.
> >
> > The internet hints that it might have to do with the version
of NPM
> used to create the package vs the NPM we are using to