From the Friday pub chat, it seems worth raising a thread on how we'll handle deploying changes.
I'm thinking we need to consider how we deploy Page Kit, and also components (be those on Bower or npm).
There are going to be differences from how we currently deploy n-ui. For context, there Bower dependencies are ranged and we rebuild all front end apps on a new n-ui tag to keep everything in sync.
With Page Kit I believe there's the possibility of having many different versions of packages like o-lazy-loading depending on the page you visit. To consider is that we don't often upgrade packages in systems like next-epaper.
We've got Renovate as a tool to support the release process. Here's the current configuration for Page Kit packages.
I'd like to come back to this with a solution or two.
From the Friday pub chat, it seems worth raising a thread on how we'll handle deploying changes.
I'm thinking we need to consider how we deploy Page Kit, and also components (be those on Bower or npm).
There are going to be differences from how we currently deploy n-ui. For context, there Bower dependencies are ranged and we rebuild all front end apps on a new n-ui tag to keep everything in sync.
With Page Kit I believe there's the possibility of having many different versions of packages like o-lazy-loading depending on the page you visit. To consider is that we don't often upgrade packages in systems like next-epaper.
We've got Renovate as a tool to support the release process. Here's the current configuration for Page Kit packages.
I'd like to come back to this with a solution or two.