Wails: Feature request: Empty skeleton

[stevesobol]

Hi. New Wails user. Very impressed.

I also recently started using Rekit Studio, which I love. It's an opinionated React-powered webapp framework with a built-in IDE.

I can also see some times when I may just want to create a simple HTML/CSS/JSS app without a framework.

I propose an new wails init template: essentially, an empty project, with just a Go module and nothing in the frontend directory. This template could be used if you want to use a framework other than one that is currently on the list, or if you don't want to use a framework at all.

Is this doable?

[leaanthony]

Hi @stevesobol - Thanks for the kind words. There's a vanilla template already there:

You can delete what's in the frontend and customise as you please.

Let us know how you get on!

[stevesobol]

Ugh. When creating my first project, I read option 3 as _VanillaJS,_ which, of course, isn't what it actually SAYS.

VanillaJS is this.

Oops. :)

Thank you.

[leaanthony]

You know what? I should change it to "Plain HTML/JS/CSS"

[leaanthony]

Also, you do know that that's a joke site advocating using plain js? 😉

[stevesobol]

HA! No, I thought it was an actual framework. I haven't had time to look at the site. But try checking any of the checkboxes on the homepage; no matter what you check, the download size remains

Final size: 0 bytes uncompressed, 25 bytes gzipped.

[stevesobol]

So... Sharing this experience so other people don't embarrass themselves like I did. O.o

[leaanthony]

So now you've learnt 2 things! 😃
Let us know if you need any help. Good luck!

[stevesobol]

I'm getting a Javascript error when I build a sample app and try to run it (using the vanilla template). Things run error-free using wails serve / npm run serve - I'm going to have to do a debug build and see what's happening.

[leaanthony]

Urgh, that's something I didn't actually try :facepalm: - I'll have a look today.

[leaanthony]

I just re-read your message. I absolutely did test that.

On Sat, 4 Jul 2020, 02:29 Steve Sobol, [e-mail] wrote:

I'm getting a Javascript error when I build a sample app and try to run it
(using the vanilla template). Things run error-free using wails serve / npm
run serve - I'm going to have to do a debug build and see what's
happening.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/wailsapp/wails/issues/450#issuecomment-653615809, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAO2SYBQUVIOYHVKRMFHDHLRZYBNLANCNFSM4ONTIIZQ
.

[stevesobol]

Hm. Well, I was running 1.6.0 and tried running wails update and discovered that I was using a rather old version. Updated to 1.7.1 and I'm going to try creating a new vanilla project.

[stevesobol]

Ahhah. Only started with Wails within the last week, not sure how I ended up with 1.6.0. But updating to 1.7.1 worked. I tried creating a new project and using wails build -d and it's running fine. Next step is to try a Rekit project! 😁

[leaanthony]

Nice one!

[stevesobol]

So, with Rekit-React, my app's entry point is build\static\main.48cc335b.chunk.js (the four-digit hex number in the middle changes, IIRC). wails build is expecting to find it in build\main.js. It would appear that I need a custom webpack config. Rekit-React normally doesn't create a webpack.json when you start a new project. This will be interesting...

[stevesobol]

I'm going to play around with my project. I should put my results up on a blog somewhere. Regardless, the problem I had is fixed :)

[leaanthony]

Configure the project as you need. Wails doesn't impose anything on you. The install and build commands are all it uses and they are configurable in project.json.