WIP Component library for Statsforvalternes Fellesorganisasjon

Adding or updating dependencies

0. In the terminal, navigate to the /packages/svelte folder
1. Run yarn install

Creating new component

0. Examine the React code of the equivalent React component 0a. If there is no React code, use your own intuition on how to implement the component and skip to step 4.
1. You will have to understand the React implementation in order to create an equivalent implementation in Svelte. You might not be able to use the exact same markup or Javascript logic.
2. In the conversion process, ensure to allow for the same props except those props which are React-specific or otherwise not possible/sensible to implement in a Svelte component
3. The ComponentName.module.css from the React-equivalent can be directly copy-pasted into the Svelte component's style block
4. Add your component's information in the package.json file in the /packages/svelte folder, under the "exports" key. Looking at existing exported components should be enough to understand the pattern to follow.
5. Ensure your component is exported from the index.js inside /lib/components

Testing your component

0. Add your component to the homepage or a route of your choosing
1. Navigate to the /packages/svelte folder
2. Run npm run dev
3. In your browser, navigate to the route you placed the component
4. You should now be able to iterate over and test your component as you would in a regular Svelte application

Publishing to NPM

0. Navigate to the /packages/svelte folder.
1. Bump the version number of the package in package.json: 0.0.x + 1.
2. Commit and push your changes.
3. Use this terminal command to publish: npm publish --access public. (This step requires you to be logged in with NPM credentials if you haven't already done so)

Build & Publish Design Tokens

0. Navigate to the root folder
1. Run yarn build 1a. You may get errors related to yarn.lock file. You can try to remove the yarn.lock file, and/or run yarn install
2. In the /packages/tokens folder, bump the version number of the package in package.json: 0.0.x + 1.
3. Navigate to the /packages/tokens folder
4. Use this terminal command to publish: npm publish --access public. (This step requires you to be logged in with NPM credentials if you haven't already done so)