Laurence de Bruxelles

Okay, v13 will now use the `npm run dev` command for local development, solving this issue.

Question, will this affect users? I think @joelanman reached out on xgov Slack a couple of times asking if it would be a problem and got no response, affirmtively or...

I think that removing v6 compatibility in an instance of the kit that has some parts using v6 and some parts not would mean that that only the parts using...

Do we want to link up this release with any release to remove docs support? I would say yes, but didn't have time in meeting today to discuss it.

I think the next step we need to take is #1308, so this is in blocked while that goes on.

We need to decide when (roughly) we're going to release this change, before we can finish and release the comms.

@NoraGDS and I agree that we should review the backwards compatibility docs before doing this release (https://github.com/alphagov/govuk-prototype-kit/issues/1184), I've added it to the tasks.

I'd like to do this as part of the release for v13 of the kit, as this is a breaking change, but something we should do soon. In my opinion...

Have not yet tried to reproduce this. --- Edited to add: it seems bad in general that uncaught errors in user defined routes can crash the app, there should be...

Another example of a test run with a flaky failure: https://github.com/alphagov/govuk-design-system/runs/4950634265?check_suite_focus=true ``` FAIL __tests__/component-options.test.js ● Component page › macro options should be opened and in view when linked to expect(received).toBe(expected)...