2
0
mirror of https://github.com/iconify/iconify.git synced 2024-11-09 23:00:56 +00:00
iconify/packages/svelte-demo
2021-08-09 09:22:08 +03:00
..
public Svelte component with API support 2021-05-01 23:38:56 +03:00
src Rebuild Svelte component: component is now a default export, svelte component is used as main export to make it work correctly with SSR 2021-05-14 21:39:12 +03:00
.gitignore Publish Svelte component, fix few typos in Vue and React documentation and demo 2020-04-28 22:40:05 +03:00
package-lock.json Update dependencies, rewrite readme files 2021-06-20 09:59:30 +03:00
package.json Publish new components as stable 2021-08-09 09:22:08 +03:00
README.md Publish Svelte component, fix few typos in Vue and React documentation and demo 2020-04-28 22:40:05 +03:00
rollup.config.js Publish Svelte component, fix few typos in Vue and React documentation and demo 2020-04-28 22:40:05 +03:00

Looking for a shareable component template? Go here --> sveltejs/component-template


svelte app

This is a project template for Svelte apps. It lives at https://github.com/sveltejs/template.

To create a new project based on this template using degit:

npx degit sveltejs/template svelte-app
cd svelte-app

Note that you will need to have Node.js installed.

Get started

Install the dependencies...

cd svelte-app
npm install

...then start Rollup:

npm run dev

Navigate to localhost:5000. You should see your app running. Edit a component file in src, save it, and reload the page to see your changes.

By default, the server will only respond to requests from localhost. To allow connections from other computers, edit the sirv commands in package.json to include the option --host 0.0.0.0.

Building and running in production mode

To create an optimised version of the app:

npm run build

You can run the newly built app with npm run start. This uses sirv, which is included in your package.json's dependencies so that the app will work when you deploy to platforms like Heroku.

Single-page app mode

By default, sirv will only respond to requests that match files in public. This is to maximise compatibility with static fileservers, allowing you to deploy your app anywhere.

If you're building a single-page app (SPA) with multiple routes, sirv needs to be able to respond to requests for any path. You can make it so by editing the "start" command in package.json:

"start": "sirv public --single"

Deploying to the web

With now

Install now if you haven't already:

npm install -g now

Then, from within your project folder:

cd public
now deploy --name my-project

As an alternative, use the Now desktop client and simply drag the unzipped project folder to the taskbar icon.

With surge

Install surge if you haven't already:

npm install -g surge

Then, from within your project folder:

npm run build
surge public my-project.surge.sh