uikit icon indicating copy to clipboard operation
uikit copied to clipboard

Examples and Fonts not found

Open kwaa opened this issue 1 year ago • 6 comments

It looks like https://pmndrs.github.io/uikit will automatically redirect to https://pmnd.rs/uikit/ and then 404 not found.

Affected URLs:

  • https://pmndrs.github.io/uikit/examples/card/
  • https://pmndrs.github.io/uikit/examples/dashboard/
  • https://pmndrs.github.io/uikit/examples/market/
  • https://pmndrs.github.io/uikit/examples/lucide/
  • https://pmndrs.github.io/uikit/examples/auth/
  • https://pmndrs.github.io/uikit/fonts/inter-light.json
  • https://pmndrs.github.io/uikit/fonts/inter-normal.json
  • https://pmndrs.github.io/uikit/fonts/inter-medium.json
  • https://pmndrs.github.io/uikit/fonts/inter-semi-bold.json
  • https://pmndrs.github.io/uikit/fonts/inter-bold.json

image

kwaa avatar Jul 15 '24 09:07 kwaa

The fonts are accessible (but having CORS issues with local development) and the example is still 404.

image

kwaa avatar Jul 15 '24 10:07 kwaa

We had a short DNS issue, but should be fixed now

bbohlender avatar Jul 15 '24 21:07 bbohlender

We had a short DNS issue, but should be fixed now

It looks like the CORS issue has reappeared (the example doesn't load the fonts correctly either), and it might be better to provide the fonts as an npm package. I can open a feature request issue if needed.

image

kwaa avatar Jul 19 '24 12:07 kwaa

yes, the team reverted the DNS changes again. But for the future this repo should switch to the default fonts beeing distributed as inlined jsons and base64 encoded textures. If you know how to set those things up (the cicd pipeline needs to run the font conversion and inline the json and the base64 encoded MSDF texture into the uikit package), I'd love to help with a PR :)

bbohlender avatar Jul 19 '24 17:07 bbohlender

So meanwhile how to solve this problem in development? (it seems to work well in Vercel deployment but not in localhost)

muhirai avatar Jul 21 '24 00:07 muhirai

The DNS error is fixed right now and should not appear in the near future, so that everybody can take their time to migrate to 0.4.0 (comming out soon), where this error cannot happen. However, since DNS entries are cached on the OS level, you might need to manually clear the DNS cache or wait a little bit until the DNS entry is reloaded for you.

bbohlender avatar Jul 21 '24 07:07 bbohlender