Re: Royale CLI issues

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

Re: Royale CLI issues

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

Re: Royale CLI issues

:) 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

Re: Royale CLI issues

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

Re: Royale CLI issues

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

Re: Royale CLI issues

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

Re: Royale CLI issues

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:

Re: Royale CLI issues

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:

Re: Royale CLI issues

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

Re: Royale CLI issues

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

Royale CLI issues

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