Jack Works
Jack Works
cc @TechQuery hi! are you available for the spec writing?
TypedArrays are used to store binary-like data, it is not representing a list of items in the thinking model so I think it is strange to support this on those.
IIRC typed arrays don't have .map, .filter etc, maybe that reason applies here
Oh so we should match them
I'd like to have an all-in-one (CJS+ESM) lodash too. It's annoying when I try to SSR and it fails with "Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: node_modules\.pnpm\[email protected]\node_modules\lodash-es\lodash.js"....
Or make a shadow package that only provides 4 files: > lodash.mjs ```js export * from 'lodash-es' ``` > lodash.cjs ```js module.exports = require('lodash') ``` > lodash.d.ts ```ts export *...
I've published https://www.npmjs.com/package/lodash-unified on npm by the method I mentioned above and it works well in our project. (But not for dependencies of our project).
> Why not go for a major new version that a purely ESM package, users that want to continue using CommonJS can simply remain on 4.x. If you wanna use...
You can use yarn/pnpm module resolution to force "lodash" to be resolved to "lodash-es". On Sun, Jan 30, 2022, 9:40 AM Charles Allen ***@***.***> wrote: > Why not go for...
> > I've published https://www.npmjs.com/package/lodash-unified on npm by the method I mentioned above and it works well in our project. (But not for dependencies of our project). > > @Jack-Works:...