ModernDash is a TypeScript-first utility library designed as a performant and lightweight alternative to Lodash, optimized for modern browsers and enhanced developer experience. Currently stable at version 4.0.2, it follows a release cadence driven by feature additions, bug fixes, and security patches, with major versions tied to breaking changes like Node.js version bumps. Key differentiators include its strict TypeScript adherence (no `any` types), ESM-only distribution, tree-shakable design, and a strong focus on outperforming Lodash in most benchmarks while maintaining zero runtime dependencies. It selectively implements only essential utility functions, encouraging the use of native JavaScript alternatives where available, contrasting with Lodash's more comprehensive API surface.
npm install moderndashVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to install ModernDash and use fundamental utility functions like `chunk`, `camelCase`, and `merge` in a TypeScript environment.
Upgrade your Node.js environment to version 20.x or newer. Alternatively, pin your `moderndash` dependency to `<4.0.0`.
Upgrade to `moderndash@4.0.1` or newer immediately to mitigate prototype pollution vulnerabilities. Review your application for any sensitive operations involving `merge` or `set`.
Migrate deprecated function calls to their native JavaScript equivalents. The library prioritizes minimal API surface and encourages native solutions where available.
Upgrade to `moderndash@4.0.2` or newer to ensure correct and comprehensive deburring of a wider range of special characters.
Refactor your import statements to use ES Module syntax: `import { chunk } from 'moderndash';` and ensure your project is configured for ESM.Update your Node.js environment to version 20 or higher. You can use a tool like `nvm` to manage Node.js versions.
Ensure your build setup (e.g., Babel, Webpack, Vite) is correctly configured for ES Modules, allowing `import` statements to resolve `moderndash` properly. Verify `"type": "module"` in your `package.json` if running in Node.js, or adjust bundler configurations.
No dependency data recorded yet.