open-index/open-npm huggingface dataset:
npm package: @opendialogai/who-lt-pwa
Description: WHO Lithuania PWA front end
Author: OpenDialog
Latest version: 1.1.0

# vue-project

This template should help get you started developing with Vue 2 in Vite.

## Recommended IDE Setup

[VSCode](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=johnsoncodehk.volar) (and disable Vetur).

## Customize configuration

See [Vite Configuration Reference](https://vitejs.dev/config/).

## Project Setup

```sh
yarn install
```

### Compile and Hot-Reload for Development

```sh
yarn run dev
```

### Compile and Minify for Production

```sh
yarn run build
```

## Publishing

Once built, the assets in the `/dist` directory can be published to NPM (https://www.npmjs.com/package/@opendialogai/who-lt-pwa) to be consumed
in the OD application.

To publish, run 

```sh
npm publish
```

## Local Development

** NB - please note, this flow does not seem to work through the docker workspace container, please run locally **

If developing locally, you can link the project by running

```sh
yarn link
```

in this project and then

```sh 
yarn link @opendialogai/who-lt-pwa
```

in the who-app project. This will link the 2 projects together - you should be able to see the symlink in the node_modules
directory in who-app.

Now there are 2 watchers to run:

1. From inside this project root, run:

```sh
yarn build-watch
```

This will watch any changes made to components and re-run the vite build process with assets being saved to `/dist`.

2. From inside the who-app project root, run

```sh
yarn watch-dev
```

This should watch for any changes in the node_modules directory and copy assets into the `public/vendor` folder.

** NB - since image paths are different for local vite dev, or production built assets, the build command sets a `base` of
`vendor/assets`. For this to work as expected, all image urls should be imported eg 

```vue
:src="require('local/path/to/asset')"
```

This will then be converted to the correct path when built and published
npm package: @opendialogai/who-pwa
Description: WHO Stars PWA front end
Author: OpenDialog
Latest version: 1.1.0

# vue-project

This template should help get you started developing with Vue 2 in Vite.

## Recommended IDE Setup

[VSCode](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=johnsoncodehk.volar) (and disable Vetur).

## Customize configuration

See [Vite Configuration Reference](https://vitejs.dev/config/).

## Project Setup

```sh
yarn install
```

### Compile and Hot-Reload for Development

```sh
yarn run dev
```

### Compile and Minify for Production

```sh
yarn run build
```

## Publishing

Once built, the assets in the `/dist` directory can be published to NPM (https://www.npmjs.com/package/@opendialogai/who-pwa) to be consumed
in the OD application.

To publish, run 

```sh
npm publish
```

## Local Development

** NB - please note, this flow does not seem to work through the docker workspace container, please run locally **

If developing locally, you can link the project by running

```sh
yarn link
```

in this project and then

```sh 
yarn link @opendialog/who-pwa
```

in the who-app project. This will link the 2 projects together - you should be able to see the symlink in the node_modules
directory in who-app.

Now there are 2 watchers to run:

1. From inside this project root, run:

```sh
yarn build-watch
```

This will watch any changes made to components and re-run the vite build process with assets being saved to `/dist`.

2. From inside the who-app project root, run

```sh
yarn watch-dev
```

This should watch for any changes in the node_modules directory and copy assets into the `public/vendor` folder.

** NB - since image paths are different for local vite dev, or production built assets, the build command sets a `base` of
`vendor/assets`. For this to work as expected, all image urls should be imported eg 

```vue
:src="require('local/path/to/asset')"
```

This will then be converted to the correct path when built and published