v1.1.8
Release Notes: Glin-Profanity v1.1.8
We are excited to announce the release of Glin-Profanity v1.1.8! This update focuses on improving compatibility and providing support for both CommonJS (CJS) and ESModules (ESM) environments, along with other enhancements.
🚀 What's New in v1.1.8
1. Dual Build Support (CommonJS & ESM)
With this release, Glin-Profanity is now built and packaged to support both CommonJS and ESModule environments. This ensures compatibility with modern bundlers like Webpack and Rollup, as well as traditional Node.js applications.
- CommonJS (CJS): Built files are available in
lib/cjs/. - ESModules (ESM): Built files are available in
lib/esm/. - UMD Build: Universal build available for broader compatibility across various environments.
2. Updated Package Structure
The package now includes a new structure for better module resolution:
exportsfield inpackage.jsonfor streamlined imports.- Updated
main,module, andtypesfields inpackage.jsonto point to the correct build files.
3. Improved Error Handling
Enhancements have been made to resolve issues related to module import errors in different environments, ensuring smoother integration in various platforms and applications.
🐛 Bug Fixes
- Fixed issues with incorrect severity levels being reported.
- Improved the handling of profane words merged into other words.
- Addressed the bug where certain complex word patterns were not correctly detected as profanity.
📦 Package Structure Changes
- Split builds into
lib/cjs/for CommonJS andlib/esm/for ES Modules. - Removed extra root files for better package size management.
⚙️ Future Plans
- Further enhancements to custom word list management.
- Additional language support and improved multilingual handling.
- Continuous integration and delivery improvements for faster release cycles.
Check out the Glin-Profanity project on GitHub or install the latest version via npm:
npm install glin-profanityOR
yarn add glin-profanityThank you for using Glin-Profanity!
What's Changed
Full Changelog: v1.1.7...v1.1.8