Update primer/css version about view_components

[colebemis]

@joelhawksley I'm sure it's possible, but it might be tricky to scope the styles so they don't conflict with Doctocat styles.

I think the easiest solution would be to use https://unpkg.com/@primer/css-next@canary/dist/primer.css, which should give us the same version that dotcom uses.

When primer/css#1131 is merged, we can go back to using https://unpkg.com/@primer/css/dist/primer.css.

[srt32]

@joelhawksley I think we are running on matching versions. Am I missing something?

[joelhawksley]

@joelhawksley I think we are running on matching versions. Am I missing something?

I see that dotcom is using `"@primer/css-next": "0.0.0-6a1daf3"., which is the release candidate for v16.

[srt32]

Interesting! How should / could we keep things up to date? I can update the unpkg link manually now but this is going to break again...

[srt32]

Looking again, https://github.com/primer/css-next is a private mirror. I'm not sure that's going to work for this project...

[manuelpuyol]

Maybe @simurai could help us here?

We want to use the same PrimerCSS version as dotcom, but it looks like that version is not publicly available for us to use, since we get the CSS from unpkg now

[joelhawksley]

@colebemis would it be possible to package and serve Primer CSS in the PVC doctocat site?

[srt32]

Aha, I was not expecting the unpkg link for css-next to exist given the repo is private ;). I made that switch in #278

[srt32]

Done via #278