Tagify v4.38.0
Modern-browser focus, React wrapper import fixes, and two user-facing bugfixes.
Breaking changes
Internet Explorer support dropped
- Removed
tagify.polyfills.min.jsand the entiresrc/polyfills/tree - Removed the gulp
polyfillstask andpackage.jsonexport browserslistnow excludes IE (not ie 11)- If you still load the polyfills bundle for legacy browsers, remove that script tag — Tagify targets evergreen browsers only
React wrapper packaging
src/react.tagify.jsx→src/react.tagify.js(JSX-free, usescreateElement)- Stale
dist/react.tagify.jsxbundle removed - All
@yaireo/tagify/reactexport paths now resolve tosrc/react.tagify.js - Removed
src/react-compat-layer.js(replaced withrenderToStaticMarkupfromreact-dom/serverfor safe template rendering)
Migration: Update imports if you referenced the old .jsx path directly. @yaireo/tagify/react should work without a custom JSX loader in webpack/Vite/Next.
Bug fixes
- #1417 — Remove button stopped working when
classNames.tagXhad multiple space-separated classes. Detection now usesmatches(classNames.tagXSelector)(first class token), consistent with other*Selectorgetters. - #1495 —
IndexSizeErrorwhen calling the Selection API with no active range.placeCaretAfterNodenow guardsrangeCountbeforegetRangeAt(0). - React — Wrapper failed to parse in bundlers that don't transpile
node_modulesJSX. Wrapper is now plain ES source consumable by any bundler without a JSX/Babel loader.
Build & tooling
pnpm buildroutes throughgulp build(production build, not watch mode)- SWC transpilation and autoprefixer driven from shared
browserslistconfig - README updated: modern-browser policy, CDN setup without polyfills bundle
- Dependency updates (
pnpm-lock.yaml)
Full Changelog: v4.37.1...v4.38.0