v3.0.0

[JumpLink]

🎉 ts-for-gir v3.0.0 is here! 🚀

This stable release brings exciting new features and improvements to ts-for-gir.

Highlights

• Support for generating NPM packages for each module, making it easier to manage and use the type definitions.
• New CLI options to generate NPM packages and customize the package scope name.
• Improved documentation with detailed explanations of the new CLI options.
• Enhanced package structure with separate folders for each package, along with individual package.json files.
• Compatibility updates for GNOME Shell extensions, including a dedicated NPM package for GNOME Shell types.
• Expanded support for ambient modules.
• Generation of both CommonJS and ESM modules.
• Breaking changes to improve file naming conventions and folder structure.
• The pre-generated NPM packages can be found on gjsify/types

Changelog

• Add support to generate a package for each type we can publish on NPM, see Add support to generate a package for each type we can publish on NPM #106
• Add a new CLI option to generate NPM packages
• Add a new CLI option to change the NPM package scope name
• Documentation for the new CLI options
• Generate a package.json for each package
• One folder for each package
• New example
• Add dependencies to each package.json
• Package names in lower case
• Separate package names for node-gtk types
• Package directory and file names in lower case
• Parse library versions
• Add a README.md for each NPM package
• Different README.md for node-gtk NPM packages
• Add an test to CI
• Fix tsconfig.alias.json
• Add support for ambient modules
• Documentation for ambient modules
• Generate both CJS and ESM modules
• Add node-gtk to the peer dependencies to the node-gtk NPM packages
• Remove destination environment directory
• Separate README.md for the main NPM packages (@gir/gjs and @gir/node-gtk)
• Generate and publish the new NPM packages
• Provide system and gettext as ESM, see Provide system and gettext as ESM #114
• Include only desired types (instead of all existing ones)
• Add repository and homepage to package.json
• Updated Documentation for the new NPM packages
• Move the GNOME Shell type definitions to a NPM package and make use of the new generated NPM packages

---

This discussion was created from the release v3.0.0.