@communitiesuk/svelte-component-library 0.1.17 → 0.1.18

package/README.md

@@ -1,58 +1,40 @@
-# Quick Start Installation
+# MHCLG Svelte Component Library
 
-Because this package is currently privately published to the GitHub npm package registry, you'll need to log in to the package registry before you can install the package. To log in you'll need your GitHub username and a personal access token with the correct permissions.
+A comprehensive component library for government digital services, built with Svelte 5 and following GOV.UK Design System principles.
 
-## 1. To get your personal access token on GitHub, follow these steps:
+## Prerequisites
 
-1.  **Log in to GitHub**: Go to your GitHub account.
-2.  **Navigate to Developer Settings**:
-    *   Click on your profile photo in the upper-right corner of the page.
-    *   Select Settings.
-    *   In the left sidebar, click Developer settings.
-3.  **Access Personal Access Tokens**:
-    *   Under the Personal access tokens section in the sidebar, click either Tokens (classic) or Fine-grained tokens, depending on your preference.
-4.  **Generate a New Token**:
-    *   Click Generate new token (for classic tokens, select Generate new token (classic)).
-    *   Provide a descriptive name in the "Note" field.
-    *   Set an expiration date if needed.
-    *   Choose the required scopes or permissions for the token. For installing the package, we will need "write:packages" (Upload packages to GitHub Package Registry), "read:packages" (Download packages from GitHub Package Registry) and "repo".
+This component library is designed for use with:
 
-5.  **Generate and Save the Token**:
-    *   Click Generate token.
-    *   Optionally, copy the new token to your clipboard for immediate use. Make sure to save it securely, as you won’t be able to view it again.
+- **SvelteKit projects** - The components are built for SvelteKit applications
 
-## 2. Next, you will need to add the GitHub registry path to the npm config file `.npmrc` so that npm knows to look for the package we want to authenticate for within the GitHub registry rather than the npm website.
+- **Svelte 5** - Components use the latest Svelte 5 syntax and runes
 
-1.  Add this line to the `.npmrc` file: `@communitiesuk:registry=https://npm.pkg.github.com`
+## Documentation and Examples
 
-## 3. Now we can log in:
+Visit our [component library documentation](https://communitiesuk.github.io/mhclg_svelte_component_library/) for:
 
-1.  Enter the following command into the terminal:
-    ```bash
-    npm login --scope=@communitiesuk --auth-type=legacy --registry=https://npm.pkg.github.com
-    ```
-2.  Enter your GitHub username, followed by the PAT token we obtained in the previous step as the password. When copying the token into the terminal, it may not be visible. Press the "Enter" key regardless and it should submit.
+- Interactive component examples
+- API documentation
+- Usage patterns and best practices
+- Installation guides
 
-> Username: USERNAME
-> Password: TOKEN
+## Quick Start Installation
 
-More information about the GitHub npm registry can be found here: [https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)
+The package is publicly available on npm:
 
-## 4. Now you are logged in, you can install the package:
-
-1.  Enter the npm install command for this package, using the latest version. The package should start installing.
+```bash
+npm install @communitiesuk/svelte-component-library@latest
+```
 
-To import a component from the newly installed package, you can add an import statement in the following structure to your Svelte page file:
+## Usage
 
-```javascript
-import { InternalHeader, NotificationBanner, WarningText, SearchAutocomplete, Accordion} from "@communitiesuk/svelte-component-library";
-```
+### GOV.UK Frontend Styles
 
-See the documentation app for examples of how to use the imported components.
+To ensure GOV.UK styles are applied correctly, add this script tag to your `app.html` file in the body section:
 
-2. To make sure govuk styles are applied correctly add this script tag to the app.html body tag section:
+```html
 
-```javascript
 <script>
     document.body.className +=
         " js-enabled" +
@@ -61,9 +43,26 @@ See the documentation app for examples of how to use the imported components.
         : "");
 </script>
 ```
+
+This is required because the GOV.UK Frontend CSS checks the document body for JavaScript availability to progressively enhance components.
+
+### Importing Components
+
+Import components directly from the package:
+
+```javascript
+import {
+  InternalHeader,
+  NotificationBanner,
+  WarningText,
+  SearchAutocomplete,
+  Accordion,
+} from "@communitiesuk/svelte-component-library";
+```
+
 # Releasing a new version of the Svelte Component Library
 
-This guide outlines the steps to bump the version of your package, tag the release in Git, and push it to prepare for publishing.
+This guide outlines the steps to bump the version of your package, tag the release in Git, and publish to npm.
 
 ## 1. Commit Your Changes
 
@@ -80,75 +79,80 @@ Make sure you are on your main development branch you want to release (e.g., `ma
 
 Use the `npm version` command to update `package.json` and `package-lock.json`, create a commit, and create an annotated Git tag. Choose **one** of the following based on [Semantic Versioning (SemVer)](https://semver.org/):
 
-*   **Patch Release (Bug fixes, tiny changes - e.g., 0.1.8 -> 0.1.9):**
-    ```bash
-    npm version patch
-    ```
-*   **Minor Release (New features, backward-compatible - e.g., 0.1.8 -> 0.2.0):**
-    ```bash
-    npm version minor
-    ```
-*   **Major Release (Breaking changes - e.g., 0.1.8 -> 1.0.0):**
-    ```bash
-    npm version major
-    ```
-*   **Specific Version:**
-    ```bash
-    npm version <new-version> # Replace <new-version> with the desired version, e.g., 1.2.3
-    ```
+- **Patch Release (Bug fixes, tiny changes - e.g., 1.0.0 → 1.0.1):**
 
-## 3. Push Changes and Tags
+  ```bash
+  npm version patch
+  ```
 
-Push the commit and the new tag created by `npm version` to your remote Git repository (e.g., GitHub):
+- **Minor Release (New features, backwards compatible - e.g., 1.0.0 → 1.1.0):**
 
-```bash
-git push && git push --tags
-```
+  ```bash
+  npm version minor
+  ```
 
-*   `git push`: Pushes the version commit.
-*   `git push --tags`: Pushes the newly created version tag.
+- **Major Release (Breaking changes - e.g., 1.0.0 → 2.0.0):**
+  ```bash
+  npm version major
+  ```
 
-## 4. Publishing (Automatic via GitHub Actions)
+This command will:
 
-Now the tag has been pushed, we can create a release on GitHub to trigger the GitHub Actions workflow defined in `.github/workflows/npm-publish-github-packages.yml`, which will handle the actual `npm publish` step to GitHub Packages.
+- Update the version number in `package.json` and `package-lock.json`
+- Create a new commit with the version bump
+- Create a Git tag with the new version number
 
-Click on "create new release" from the repo homepage.
+## 3. Push Changes and Tags
 
-Choose the target branch that you want to release (e.g. main).
+Push the commit and the new tag created by `npm version` to the remote Git repository (e.g., GitHub):
 
-Choose the tag version pushed to GitHub in a previous step.
+```bash
+git push && git push --tags
+```
 
-Click generate release notes, and add any additional write-up to describe the changes in this release.
+- `git push`: Pushes the version commit.
+- `git push --tags`: Pushes the newly created version tag.
 
-Amend the release title to something appropriate, including the version number in the title.
+## 4. Create a GitHub Release
 
-Click "Set as pre-release" given the package is not stable yet.
+1. Go to the GitHub repository
+2. Click on "Releases" in the right sidebar
+3. Click "Create a new release"
+4. Select the tag you just created (e.g., `v1.0.1`)
+5. Add a release title and description
+6. Click "Publish release"
 
-Click the publish release button.
+## 5. Automatic Publishing
 
-If you now go to the "Actions" tab in the repo's horizontal nav bar, you'll see the publish workflow being triggered. Once complete, the package will be uploaded and the new version can be installed.
+Once you create the GitHub release, If you now go to the "Actions" tab in the repo's horizontal nav bar, you'll see the publish workflow being triggered. The GitHub Actions workflow (`.github/workflows/npm-publish.yml`) will automatically:
 
-# create-svelte
+- Build the package
+- Publish it to npm public registry
+- Make it available for installation via `npm install @communitiesuk/svelte-component-library`
 
-Everything you need to build a Svelte library, powered by [`create-svelte`](https://github.com/sveltejs/kit/tree/main/packages/create-svelte).
+## 6. Verify the Release
 
-Read more about creating a library [in the docs](https://svelte.dev/docs/kit/packaging).
+After the GitHub Action completes, verify that your package was published successfully:
 
-## Creating a project
+1. Check the [npm package page](https://www.npmjs.com/package/@communitiesuk/svelte-component-library)
+2. Try installing the new version in a test project:
+   ```bash
+   npm install @communitiesuk/svelte-component-library@latest
+   ```
 
-If you're seeing this, you've probably already done this step. Congrats!
+## Notes
 
-```bash
-# create a new project in the current directory
-npx sv create
+- Only create releases from the "main" branch to ensure stability
+- Always test changes thoroughly before creating a release
+- Consider creating pre-release versions for testing: `npm version prerelease --preid=alpha`
 
-# create a new project in my-app
-npx sv create my-app
-```
+# Developing and Building Commands
+
+This project is built with [`create-svelte`](https://github.com/sveltejs/kit/tree/main/packages/create-svelte). Read more about creating a library [in the docs](https://svelte.dev/docs/kit/packaging).
 
 ## Developing
 
-Once you've created a project and installed dependencies with `npm install` (or `pnpm install` or `yarn`), start a development server:
+Start a development server:
 
 ```bash
 npm run dev
@@ -176,13 +180,3 @@ npm run build
 You can preview the production build with `npm run preview`.
 
 > To deploy your app, you may need to install an [adapter](https://svelte.dev/docs/kit/adapters) 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](https://opensource.org/license/mit/)).
-
-To publish your library to [npm](https://www.npmjs.com):
-
-```bash
-npm publish
-```

package/dist/components/data-vis/line-chart/Line.svelte

@@ -13,7 +13,6 @@
   } from "d3-shape";
 
   import { scaleLinear } from "d3-scale";
-  import LineChart from "../../../../routes/playground/create-a-reactive-line-chart-camilla/local-lib/LineChart.svelte";
 
   let {
     dataArray,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@communitiesuk/svelte-component-library",
-  "version": "0.1.17",
+  "version": "0.1.18",
   "repository": {
     "type": "git",
     "url": "https://github.com/communitiesuk/mhclg_svelte_component_library.git"