Releases: Coder-Spirit/nominal
Releases · Coder-Spirit/nominal
nominal@4.0.3 , nominal-inputs@1.0.3 , safe-env@1.0.0
Minor Releases
@coderspirit/nominal
(v4.0.3): minor internal & build refactor changes
New Packages
@coderspirit/nominal-inputs
(v1.0.3): new library with "input types" to be used in stricter function signatures .@coderspirit/safe-env
(v1.0.0):- we ported
safe-env
from its "old" repository to this one to ensure better maintenance - this is the first stable release of this library
- its API has been completely overhauled to ensure that is useful for more people
- we ported
nominal@4.0.0 & nominal-symbols@2.0.0
Breaking Changes
- We raised the required NodeJS and TypeScript versions, to v18 and v5.2 respectively.
- "Minor" changes in how we build the files that are later distributed, because this affects the unique symbols that are exported, it is a breaking change.
Internal Development Changes
- We moved
@coderspirit/nominal-symbols
to the same repository as@coderspirit/nominal
. - We now rely on a centralised package for our Prettier, ESLint and TypeScript configurations.
- We improved our tests by switching from Jest to Vitest, which is much simpler to use, and also much faster.
- We now use Turborepo to manage the dependencies between task in the project.
Commits
3.2.2
3.2.1
3.2.0
3.1.0
New Features
- Export
FastBrand
andFastFlavor
for faster compilation times when we want to add brands or flavors on "basic" types.
Backwards & Forward Compatibility
- For CommonJS "imports", rely on the newly extracted package
@coderspirit/nominal-symbols
. The unique symbols where extracted into a new (and more stable) package to minimize the probability of breaking compatibility if different versions of Nominal coexist in the same application. - For Deno and ES module imports, the "old" symbols file is still used, because NodeJS and Typescript are still quite behind on support for ES modules.