Svelte app depending on frifaktura-v2-api
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
nikobojs d4165805de fix: console.logs 2 years ago
.vscode feat: [WIP] i18n 2 years ago
public refactor: use modal for log in 2 years ago
src fix: console.logs 2 years ago
.env.example initial commit 2 years ago
.gitignore initial commit 2 years ago
README.md initial commit 2 years ago
package-lock.json refactor: much ui stuff 2 years ago
package.json feat: lots of styling 2 years ago
postcss.config.js initial commit 2 years ago
rollup.config.js feat: lots of styling 2 years ago
tsconfig.json fix: provide fallback mechanism to i18n missing keys 2 years ago

README.md

frifaktura-v2-frontend

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

Get started

Install the dependencies...

cd frifaktura-v2-frontend
npm install

Create a new file .env and paste the environment variables from .env.example

cp .env.example .env

Run the app with Rollup:

npm run dev

Navigate to localhost:5050. 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.

If you’re using Visual Studio Code we recommend installing the official extension Svelte for VS Code. If you are using other editors you may need to install a plugin in order to get syntax highlighting and intellisense.

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 Vercel

Install vercel if you haven’t already:

npm install -g vercel

Then, from within your project folder:

cd public
vercel deploy --name my-project

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