Almost 10 months after releasing v1, we are now releasing SQL Frames v2.
This version comes with some breaking changes. However those who rely on the provided main.mjs
to load SQL Frames will not experience any disruption. Only those who have custom build may need to
adjust their build scripts. If you run into any problem, reach out to us.
Apart from several quality fixes, the key breaking changes are related to improved security and
interoperability. Here are the list of breaking changes from the release notes
and what they mean.
The good thing with this is it reduces additional build dependencies. But it also has some downsides
like difficult to ensure valid markup, runtime parsing of the strings. By moving away from
we are now able to leverage standard typescript react compilation.
- Security of 3rd party libraries To avoid man-in-the-middle attacks, it is important to validate
that provide such integrity guarantees.
- Isolated require context The OOTB main.mjs uses
require.js to load several dependencies. Earlier
these dependencies were all loaded into the global context. This can conflict with rest of the app. To avoid
this starting from v2, all dependencies including SQL Frames are loaded within an isolated context.
We are glad to see the SQL Frames product being leveraged in multiple production deployments and are
relentlessly working on improving all aspects of the product.