[Resolved] Crayons does not render components as expected

Happening Incidents
1
Incident ID: INC-14
Date and Time: Fri, 28 Oct 2022 ~19:00:00 IST (approx)
Impact: All the web applications that rely on crayons
Duration For a few hours, our first report was at 17:00:00 IST

Crayons is served to all the web applications using UNPKG. In the past 24 hours, there have been a total of 82 outages reported from 24 countries.

Since Crayons relies on UNPKG, developers using Crayons are expected to face rendering issues with crayons. At the moment, few regions seem to see this up and running.

2 Likes
2

If you are still seeing problems with loading the Crayons in your apps during development, you can try to include the following alternative scripts:

<script async type="module" src="https://cdn.jsdelivr.net/npm/@freshworks/crayons@v4/dist/crayons/crayons.esm.js">
</script>
<script async nomodule src="https://cdn.jsdelivr.net/npm/@freshworks/crayons@v4/dist/crayons/crayons.js">
</script>

Ensure you use @4, and @3 to use relevant versions. No version mention will point to version 2 as follows in the inclusion scripts.

v4

https://cdn.jsdelivr.net/npm/@freshworks/crayons@v4/dist/crayons/crayons.esm.js
https://cdn.jsdelivr.net/npm/@freshworks/crayons@v4/dist/crayons/crayons.js
https://cdn.jsdelivr.net/npm/@freshworks/crayons@v4/css/crayons-min.css

v3

https://cdn.jsdelivr.net/npm/@freshworks/crayons@v3/dist/crayons/crayons.esm.js
https://cdn.jsdelivr.net/npm/@freshworks/crayons@v3/dist/crayons/crayons.js
https://cdn.jsdelivr.net/npm/@freshworks/crayons@v3/css/crayons-min.css

v2

https://cdn.jsdelivr.net/npm/@freshworks/crayons@v2/dist/crayons/crayons.esm.js
https://cdn.jsdelivr.net/npm/@freshworks/crayons@v2/dist/crayons/crayons.js

default

https://cdn.jsdelivr.net/npm/@freshworks/crayons/dist/crayons/crayons.esm.js
https://cdn.jsdelivr.net/npm/@freshworks/crayons/dist/crayons/crayons.js
2 Likes
3

To our observation, this outage lasted about ~5.5 hours, starting 28 Oct 2022, 5:00 PM IST until 28 Oct 2022, 10:21 PM IST. Our latest observation suggests that issue is now resolved.

3 Likes