Twilight

> Also is it possible for me to use the image's as links because as I see, only accepts buffer feed? https://github.com/Brooooooklyn/canvas/blob/main/index.d.ts#L191 You can use `fs` to convert local files...

@0zul I guess this issue is closable since this lib supports registering custom fonts as well as a utility function to create `Image`? Fonts can be registered with the help...

This seems to be a bug (maybe) with nextjs https://github.com/vercel/next.js/issues/30692

@dhavalveera yesterday I went through different solutions I found and somehow PWA started to work after updating my config to ```js const withPWA = require("next-pwa"); const runtimeCaching = require("next-pwa/cache"); module.exports...

I was able to do it using: ```js addEventListener("fetch", async (event) => { const response = await server.inject(event.request); event.respondWith(new Response(response.body, { // for some reason, it throws error with pogo's...

> Minimal code to reproduce the problem: > > ```ts > await new Rank() > // some other configs params... > .renderEmojis(true) > .build({ fontX: "Arial", fontY: "Arial" }); >...

And yes, `.renderEmojis` was removed, it basically does nothing in the latest version. It exists for backwards compatibility (only in terms of API)

> Okay, I'm removed `{ fontX: "Arial", fontY: "Arial" }` from `build()` and `.renderEmojis(true)`, but emojis don't rendered :( Yeah, that's because there is no font available that accepts unicode...

ref https://github.com/Brooooooklyn/canvas/issues/511

@LWJerri that could also work but im thinking about implementing it via `.renderEmojis` method