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

Checking test failures in use-govuk-frontend-v5 #367

Closed

Conversation

marcotranchino
Copy link
Contributor

What’s changed

Identifying a user need

govuk-frontend

As govuk-frontend encourages its use within
script type=module, we need to create a
separate entry for it as we do not want
any downstrema project to change the way they write
their own javascript.

This PR
- adds a new zgovuk_frontend.js` include to core layout
- removes `all.js` import from `govuk_tech_docs.js`
- creates a new `govuk_frontend_all.js` entry in
the lib that imports `all.bundle.js` from the
NPM package
- adds a new `govuk_frontend.js` entry point in
the example project that pulls in the
`govuk_frontend_all.js` from the lib
- adds new minifier - https://github.com/ahorek/terser-ruby
as the built-in one doesn't support ES6
To do: see if we can configure to silence warning

Built-in sassc compiler doesn't compile
stylesheet do to them, containing source maps

https://github.com/sass-contrib/sassc-embedded-shim-ruby
No longer needed with the upgrade to v5
@marcotranchino marcotranchino changed the title Use govuk frontend v5 silence dart sass warnings bis Checking test failures in use-govuk-frontend-v5 Sep 23, 2024
@marcotranchino
Copy link
Contributor Author

The test failures are intermittent and unrelated to the change at #364

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.

2 participants