Skip to content

Releases: typeconf/typeconf

Typeconf 0.3.0

06 Apr 07:13
1c8f7a1

Choose a tag to compare

New major release of Typeconf!

Warning: It contains breaking changes.

What's Changed

  • Add validation for reading configs by @chebykinn in #15
  • Add SDK support for reading configurations from the cloud storage. by @DMokhnatkin in #17
  • Enable multiple configs by @chebykinn in #19
  • New API -> readConfig.

For more info read the article in our blog: https://typeconf.dev/blog/launching-typeconf-storage

Full Changelog: v0.2.10...v0.3.0

Typeconf v0.2.10

21 Feb 07:22
844c2eb

Choose a tag to compare

What's new

  • Removed the dependency on @typeconf/sdk in the generated configs, now you don't need to install it. If you're using Next, just install @typeconf/react-sdk.

Typeconf v0.2.8

05 Feb 18:47
8e8d627

Choose a tag to compare

What's Changed

  • Allow using Typeconf in existing project

Starting from this release you don’t have to create a separate package for configuration, you can just add configs to your project. Check out the guide for more information: https://docs.typeconf.dev/getting-started/incremental-adoption

Full Changelog: v0.2.1...v0.2.8

Typeconf v0.2.0

24 Dec 03:24
b1d96fb

Choose a tag to compare

This release completely simplifies the way you can use Typeconf!

Instead of a separate CLI, we now have a helper called create-typeconf-package that creates the configuration package.
The configuration package allows you to call typeconf via npm run build.

Try it out now: npx create-typeconf-package <config-dir>!