https://github.com/bartosz-dude/neutralino-solid-vite

neutralino template with solid + vite with configured frontend api
https://github.com/bartosz-dude/neutralino-solid-vite

Last synced: about 2 months ago
JSON representation

neutralino template with solid + vite with configured frontend api

• Host: GitHub
• URL: https://github.com/bartosz-dude/neutralino-solid-vite
• Owner: bartosz-dude
• Created: 2024-04-21T15:56:59.000Z (5 months ago)
• Default Branch: main
• Last Pushed: 2024-04-21T16:40:27.000Z (5 months ago)
• Last Synced: 2024-05-14T00:53:58.264Z (4 months ago)
• Language: TypeScript
• Size: 24.4 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-neutralino - neutralino-solid-vite - Starter template for Neutralinojs with Solid + Vite and configured native API (Boilerplates)

README

        
# neutralino-solid-vite

[Neutralino](https://neutralino.js.org/) app template with [solid](https://solidjs.com), vite and typescript for the frontend.

## Features

- configured neutralino frontend api

- frontend HMR support

- `dev` and `build` npm scripts

## Installation

Clone this repo

```bash

git clone https://github.com/bartosz-dude/neutralino-solid-vite.git

```

Next you run this npm script in the root folder of your project

```bash

npm install

```

This will install all dependencies and neutralino binaries

## Known problems

- When closing app window in dev mode, vite doesn't stop

- may not work on first start (white screen); restart should make it work

## Why the env

Neutralino requires `__neutralino_globals.js` in `index.html` on frontend to properly connect the frontend server to neutralino server.

Docs say to use patching from neutralino config on `index.html` when using dynamic neutralino port. This only works in dev.

Static neutralino port fixes this, but throws an error when trying to open second release instance.

Using `%PUBLIC_URL%` makes vite throw an `URI malformed` error in dev when using dynamic port, but works in release.

Using the vite env makes so that patching is used in dev and `%PUBLIC_URL%` in release.