We all know that ES6 introduced template literals via which we can write a string. But there's a catch if the template is a string variable - such as when you have multilingual error messages coming from a database. Is there another way...
So I'm writing various library components using TypeScript that are targeted at Konva and I want the components to be usable in Vanilla JS without being opinionated about where Konva's JavaScript is located. What?
I'm writing a JavaScript lib with TypeScript, using the excellent Vite for on-the-fly transpiling and packaging. This post is about the configuration that I use and specifically covers removal of comments.
Various use cases require the ability to save multiple _frames_ from a canvas as an animated GIF. This isn't something the canvas can do out of the box. Lets dig into how to make it happen...
FIXED: Brave browser has a sophisticated approach to protect from browser fingerprinting. Unfortunately this makes for problems for legitimate canvas apps. In this post I investigate, try to explain what I found and suggest a work-around.
Someone on the Konva Discord group had an issue loading a complex canvas on mobile via the Konva.Node.create() process. The app works fine on desktop but iPhone Safari is complaining about the canvas being too large. What gives?
Konva's clipFunc is usually used to trim off the edges of oversize images. The magic here is that if we draw an outer path clockwise and an inner path counter-clockwise, the area defined by the inner path becomes a hole! Let's look into it...
Konva has 2 ways of making things mvoe or change - the tween and the animation. Animations are more involved but more capable, whilst tweens are a simple option if the needs are few. In this short post we look at a simple tween.