@yaireo/tagify 4.38.0

v4.38.0

on Node.js Yarn

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.js and the entire src/polyfills/ tree
• Removed the gulp polyfills task and package.json export
• browserslist now 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, uses createElement)
• Stale dist/react.tagify.jsx bundle removed
• All @yaireo/tagify/react export paths now resolve to src/react.tagify.js
• Removed src/react-compat-layer.js (replaced with renderToStaticMarkup from react-dom/server for 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.tagX had multiple space-separated classes. Detection now uses matches(classNames.tagXSelector) (first class token), consistent with other *Selector getters.
• #1495 — IndexSizeError when calling the Selection API with no active range. placeCaretAfterNode now guards rangeCount before getRangeAt(0).
• React — Wrapper failed to parse in bundlers that don't transpile node_modules JSX. Wrapper is now plain ES source consumable by any bundler without a JSX/Babel loader.

Build & tooling

• pnpm build routes through gulp build (production build, not watch mode)
• SWC transpilation and autoprefixer driven from shared browserslist config
• README updated: modern-browser policy, CDN setup without polyfills bundle
• Dependency updates (pnpm-lock.yaml)

Full Changelog: v4.37.1...v4.38.0