DEV Community

"Nextron": Electron + Next.js dream

Shiono Yoshihide on May 05, 2018

I'm a .NET developer in Japan usually, but I love to write JavaScript/TypeScript in my spare time. This article introduces Nextron, which can make...

Read full post

Ronald Flores Sequeira • May 7 '18

Wow I never expected to find what I need so randomly, I'll test it on the week.

Shiono Yoshihide • May 7 '18

I'm very glad to hear that!
Could you let me know how it was, afterwards?
On my side, I'll test it by developing markdown editor, too :)

Ronald Flores Sequeira • May 7 '18

I'm testing on windows, at the moment Windows build don't finish. (My target with electron is Windows and I work on Windows) I'm gonna try on Linux. From Nextron can could it be possible to choose build OS? (I'm new to elctron)

Shiono Yoshihide • May 7 '18

For now, default yarn build command generates all platform builds.
Ok, I'll add build options for each platform today :)

Ronald Flores Sequeira • May 7 '18 • Edited

This is what happens with Build

Shiono Yoshihide • May 7 '18

Could you run node node_modules/nextron/build/javasript/start.js?

Above is internal yarn dev.

This may be webpacking main process error, so above command would tell us something.

Or, you use latest nextron(0.2.*)?
If so, i'm sorry for bugs i know that, and i'll fix them tonight(in Japan time).

nextron v0.1.* might work for you.
(npm install --global nextron@0.1.*)

Ronald Flores Sequeira • May 7 '18

yarn dev runs well, not the node command. No problem all code have bugs, I'll test with version 0.1.

Ronald Flores Sequeira • May 7 '18

The same error with 0.1. Just to be sure if it was my OS I tested whit github.com/SimulatedGREG/electron-vue and does build and make de package for windows (the installer and .exe).

Ronald Flores Sequeira • May 7 '18

I'll test later on my PC (I'm at work right now)

Shiono Yoshihide • May 8 '18

I'm testing it on my Mac, then nextron@0.3.2(now latest) can build all packages.

Your error may be npx's bug, which is containing spaces in directory path.
So I decided to change code like below:

<FROM>
exec('npx webpack --config=***', { cwd })

<TO>
exec('node_modules/.bin/webpack --config=***', { cwd })

So avoid npx bugs, Nextron has no requirements like npm >= 5.2 now!

Ronald Flores Sequeira • May 8 '18 • Edited

I'm on my way to work, i'll test it, another option could be that Windows don't support build for OS X

Shiono Yoshihide • May 8 '18

nextron@0.3.4 is now released, which fixes yarn build error problem mainly on Windows!
(I tested Windows 7 (64bit) :)

Ronald Flores Sequeira • May 8 '18

It fail the first time, but on the second try it succeed.
(Windows 10 Home x64)

Ronald Flores Sequeira • May 8 '18

Thanks for the hard work, I'll keep testing it, hope to see great support for the project, already 1k download.

Shiono Yoshihide • Jul 4 '18

Fix almost all bugs, now released nextron@0.6.1 <3

Upgraded dependencies:

electron@^2.0.4
next@6.1.1

Peer dependencies:

react@^16
react-dom@^16

Here is sample:

$ nextron init test-app
$ cd test-app

# run development mode
$ yarn dev

# release build
$ yarn build

Ronald Flores Sequeira • Jul 4 '18

Glad to hear that,I'll be testing later in the day.

Shiono Yoshihide • Jul 8 '18 • Edited

Implemented some examples like Material UI <3

You can try it by the command like below:

# Install latest nextron
$ npm i -g nextron@latest
$ nextron -v
nextron v0.7.5

# Init a nextron app with material-ui
$ nextron init test-app --template with-javascript-material-ui

# If you are typescript lover, you can also try typescript one :)
$ nextron init test-app --template with-typescript-material-ui

# Then, start the app
$ cd test-app
$ yarn (or `npm install`)
$ yarn dev (or `npm run dev`)

Hope you can see it:

devrnsistema • Sep 1 '20

how do I be able to access the pages with the application and production, developing access normally by port 8888, but in production how do I do?