nodes/packages/ui
2024-04-24 01:40:04 +02:00
..
src feat: load props from node store 2024-04-24 01:40:04 +02:00
static feat: add validation to include_definition macro 2024-04-18 15:40:41 +02:00
.eslintignore feat: extract graph-interface into seperate package 2024-04-10 15:40:01 +02:00
.eslintrc.cjs feat: extract graph-interface into seperate package 2024-04-10 15:40:01 +02:00
.gitignore feat: extract graph-interface into seperate package 2024-04-10 15:40:01 +02:00
.npmrc feat: extract graph-interface into seperate package 2024-04-10 15:40:01 +02:00
package.json feat: add theming support 2024-04-19 01:27:11 +02:00
README.md feat: extract graph-interface into seperate package 2024-04-10 15:40:01 +02:00
svelte.config.js feat: extract graph-interface into seperate package 2024-04-10 15:40:01 +02:00
tsconfig.json feat: extract graph-interface into seperate package 2024-04-10 15:40:01 +02:00
vite.config.ts feat: extract graph-interface into seperate package 2024-04-10 15:40:01 +02:00

create-svelte

Everything you need to build a Svelte library, powered by create-svelte.

Read more about creating a library in the docs.

Creating a project

If you're seeing this, you've probably already done this step. Congrats!

# create a new project in the current directory
npm create svelte@latest

# create a new project in my-app
npm create svelte@latest my-app

Developing

Once you've created a project and installed dependencies with npm install (or pnpm install or yarn), start a development server:

npm run dev

# or start the server and open the app in a new browser tab
npm run dev -- --open

Everything inside src/lib is part of your library, everything inside src/routes can be used as a showcase or preview app.

Building

To build your library:

npm run package

To create a production version of your showcase app:

npm run build

You can preview the production build with npm run preview.

To deploy your app, you may need to install an adapter for your target environment.

Publishing

Go into the package.json and give your package the desired name through the "name" option. Also consider adding a "license" field and point it to a LICENSE file which you can create from a template (one popular option is the MIT license).

To publish your library to npm:

npm publish