We broke our own plugin and didn’t notice soon enough.

Not exactly the update I wanted to write, but probably one worth writing.

Around the time Framer 3.0 rolled out, there were changes on the plugin development side, including a breaking v4.0.0 release. Somewhere between building, shipping, and assuming everything was still doing what it was supposed to do, we missed it.

And then someone bought the plugin.

They ran it.

The report came back blank.

That was the moment we found out.

There is a particularly uncomfortable kind of embarrassment in having someone trust something you built with their money, only for them to be the person who discovers that it is broken.

We could blame an update. Technically, the update is what broke compatibility.

But keeping up with the platform our product is built on is our responsibility, not Framer’s.

We should have caught it before a customer did.

So for the last few days, we went back into it, found what had broken, fixed it, tested it again, and went through the process of getting everything back where it should be.

It is now fixed, working, and officially approved again.

This also changed something in how we are going to maintain the plugin going forward. We will be keeping a much closer eye on Framer’s developer documentation, API changes, and changelog instead of treating a working release as something that will simply stay working.

Software moves. The things underneath your software move too.

We learned that one the hard way.

If you were waiting to try the plugin, it is working again now.

And if you ever run into something that isn’t, email us directly at contact@valorsic.studio

I would much rather hear about a problem and fix it than pretend we never have them.

Pujan Aggarwal

Founder, Valorsic Studio

We broke our own plugin and didn’t notice soon enough.

Not exactly the update I wanted to write, but probably one worth writing.

Around the time Framer 3.0 rolled out, there were changes on the plugin development side, including a breaking v4.0.0 release. Somewhere between building, shipping, and assuming everything was still doing what it was supposed to do, we missed it.

And then someone bought the plugin.

They ran it.

The report came back blank.

That was the moment we found out.

There is a particularly uncomfortable kind of embarrassment in having someone trust something you built with their money, only for them to be the person who discovers that it is broken.

We could blame an update. Technically, the update is what broke compatibility.

But keeping up with the platform our product is built on is our responsibility, not Framer’s.

We should have caught it before a customer did.

So for the last few days, we went back into it, found what had broken, fixed it, tested it again, and went through the process of getting everything back where it should be.

It is now fixed, working, and officially approved again.

This also changed something in how we are going to maintain the plugin going forward. We will be keeping a much closer eye on Framer’s developer documentation, API changes, and changelog instead of treating a working release as something that will simply stay working.

Software moves. The things underneath your software move too.

We learned that one the hard way.

If you were waiting to try the plugin, it is working again now.

And if you ever run into something that isn’t, email us directly at contact@valorsic.studio

I would much rather hear about a problem and fix it than pretend we never have them.

Pujan Aggarwal

Founder, Valorsic Studio