Error while packaging a JavaScript file not in a subfolder about forge

[MarshallOfSound]

@ahadcove Your JS files must be inside a directory (not just sitting in the top level of your app). I.e. If you move main.js to be somewhere like src/main.js and update your package.json accordingly the packaged version will work.

/cc @malept We should probably catch this issue ourselves

[MarshallOfSound]

• Does it work with a simple electron-forge start
• How are you requiring main.js, is it your entry point?

[ahadcove]

Well when I use START the same thing is happening when I was using electron-packager: A static index.html with the loading text that I have when starting up my electron app for the first time.
It suppose to route to my home as soon as it starts though as it does when I have a simple ng build.

I am requiring main.js as my entry point.

in my Package.json the main field is:

"main":"main.js"

[ahadcove]

I switched the directories and everything and it does get past the error. I am still running into the static index.html though.

For some reason, I just can't figure out how to make my App work all packaged up

[MarshallOfSound]

@ahadcove I am not too familiar with the intricacies of Angular 2, can you explain what you mean by "static index.html". I don't quite understand the issue you are having.

[ahadcove]

Well my original problem was that when I run my project with ng build or ng serve it works 100% all the routers and everything just works.
It was when I started trying to package up my app with electron-packager, builder, and forge where I get the routes no longer working. Instead of loading up the Index.html then immediately navigating to my home component it stays at the index.

[MarshallOfSound]

This sounds familiar from an Electron issue. I believe it is due to how in Electron your Angular app is served from a file:// url which angular routers do not like or expect.

[ahadcove]

Hmmm That sounds like where my problem may lie, but Why would it work with ng serve and build?

[MarshallOfSound]

@ahadcove ng serve runs a localhost server I believe, so it will be served over something like http://localhost:1234

[ahadcove]

Okay so it may have something to do with Hash Locations or something
I will dig a little deeper. I may come back to forge later when I figure this out. Thanks for everything

[MarshallOfSound]

@ahadcove FWIW this is not a -forge or -packager issue, it is purely an issue with Angular 2 in Electron in general.

This might help you out
electron/electron#6799 (comment)

It looks like you need

document.write('<base href="file://' + __dirname + '/"/>');

To use a router in Angular in Electron

[ahadcove]

Yes, I have that in my index.html already. That is what get's routers working. I have a fully working angular 2 Electron app already, its just when I package it with anything it no longer functions how it should be

[MarshallOfSound]

Is the app public, I'm happy to dive into it and see what's going on?

[ahadcove]

Sadly, it's not. I'm going to keep picking away at it though. I definitely like the idea of forge though so I may be back when I get this figured out. Thank you for everything