b5fcfdfeab
At first we wanted to only support ESM. But as we want to share types and export design tokens from the react package to the outside world in order to allow local cunningham.ts files to import them, we are forced to also build the library for CJS too. Why? Because local cunningham.ts files are loaded as CJS, so they can only import CJS module. Why loading cunningham.ts as CJS? Because the tokens package's binary is built for CJS, then it's seamless to make it load CJS, where making it load ESM was buggy. And why not migrate the tokens package to ESM so? Because it implies to rewrite every imports with .js extensions, makes us loose the possibility to use __dirname kind of variables. And also Jest use for testing is not compliant at all when it comes to execute ESM code. Well, the ecosystem is not ready for that at the moment, sadly.
🎨 Cunningham, the best OpenSource Design System
Getting started
Everything is detailed on our documentation. 📚
Contributing
Please see our contributing guidelines.
License
This work is released under the MIT License (see LICENSE).