This is how easy the setup with vite is
If you need custom runtime settings, just create a file named node-red.settings.ts in the root of your project. IT IS FULLY TYPED!
To start the dev server with the latest node-red runtime, run pnpm vite
If you need a different version, configure nodeRedLauncherOptions.runtime.version with the version you need. For example,
If you need different runtime settings for different environments, configure nodeRedLauncherOptions.runtime.settingsFilepath with the path to a different settings.ts file. When this property isn't set, the plugin tries to use settings located at ./node-red.settings.ts
To build your production distro, run pnpm build.
By default, the following 3 files/dir are always copied to dist:
- LICENSE
- README.md
- examples
Your license is also added to the begining of your index.html
The package.json in the dist folder is automatically generated containing only the dependencies that were actually used by the server-side code. Client-side dependencies are bundled with your distro, and properly broken into smaller chunks.
Soon this plugin and the core library will be packaged. At the moment imports will be @allanoricil/nrg/core and @allanoricil/nrg/vite. However, If the node-red core team (@knolleary, @dceejay, @hardillb)review and let me publish these under the @node-red namespace, then imports will be @node-red/nrg/core and @node-red/nrg/vite, which would look way more professional.
This is the directory structure of an nrg project
.
├── client/
│ ├── assets
│ ├── components
│ ├── icons
│ ├── nodes
│ ├── public
│ └── index.ts
├── server/
│ ├── nodes
│ ├── schemas
│ └── index.ts
├── locales/
│ ├── docs/
│ │ └── {node-type}/
│ │ └── {en-US|pt-BR|...}.{md|html}
│ └── labels/
│ └── {node-type}/
│ └── {en-US|pt-BR|...}.json
├── examples/
│ └── 01-example.json
├── package.json
├── LICENSE
├── README.md
├── node-red.settings.ts
└── vite.config.ts
