Laurence de Bruxelles

Hi @statshan, Thanks for raising this issue, and thanks for sharing your work in this space! This looks like quite a complex issue, and it's going to want changes in...

> @lfdebrux hi I am not sure how I raise an issue against those lines? Sorry I don't use GitHub a lot! No worries, I've taken the liberty of doing...

> Also @lfdebrux sorry - when you mentioned pointing to the GSS guidance that would be great - do you know what sort of timeline that would have though? And...

We're removing jquery bit by bit: - [x] #1418 - [x] #1427 - [x] #1448

I've tried looking at this with the performance tab of the Chrome DevTools; it's hard to reproduce because the jump doesn't seem to happen if you just reload the page,...

Blocked on time.

@EoinShaughnessy ignore my last (now deleted comment), I had got myself confused. I think you are right, this should go in 'Updating to Version 12', maybe with a small qualifier...

@EoinShaughnessy at the end, they should make sure they've completed the update and everything is still working before committing and pushing changes.

I was thinking the other day (for an unrelated issue about dev dependencies and Glitch) that really we should have two npm scripts, `dev` and `serve`, that run the appropriate...

We've agreed for v13 to make the common default npm command, `npm start`, run the kit in 'production' mode. This is a breaking change, but makes it much less likely...