Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move govuk components to another repo #477

Merged
merged 2 commits into from
Feb 26, 2024
Merged

Move govuk components to another repo #477

merged 2 commits into from
Feb 26, 2024

Conversation

dabreegster
Copy link
Contributor

I moved all the common govuk Svelte components to https://github.com/acteng/govuk-svelte, since we'll want to use these in more projects. No behavioral change here.

@@ -47,6 +47,7 @@
"@turf/nearest-point-on-line": "^6.5.0",
"@turf/random": "^6.5.0",
"govuk-frontend": "^5.1.0",
"govuk-svelte": "github:acteng/govuk-svelte",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could publish to NPM, but it might encourage other people to take a dependency on them, despite the warnings in the README. For the moment, I think the git dependency is simpler. When we need to update the components, we commit in the other repo, then npm i govuk-svelte here to update the pinning in package-lock.json.

I can publish to NPM if you prefer though

@dabreegster
Copy link
Contributor Author

Rebased. The test failure looks like a flake to me, but will see what the rerun looks like

@dabreegster dabreegster merged commit 176c662 into main Feb 26, 2024
2 checks passed
@dabreegster dabreegster deleted the refactor_govuk branch February 26, 2024 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants