John-David Dalton
John-David Dalton
With `sqlite3` there are WASM alternatives that may simplify cross-platform issues: https://www.npmjs.com/package/node-sqlite3-wasm
@prabhu Yes, I'm up for attempting it!
A deprecation message should not affect another project. Besides the deprecation message (which should be harmless) are you seeing any other issue?
Keeping in mind poor perf is something that can generally be improved and ES6+ additions tend to have plenty of things to improve on that front... a single Get in...
> The entire reason for this proposal is because the committee did not want magic behavior for Namespace objects; they wanted a general-purpose solution. I don't think these are mutually...
I don't see it specified in this proposal but is the idea that for namespace objects it would be non-enumerable, non-configurable, non-writable like the namespace [`@@toStringTag`](https://tc39.github.io/ecma262/#sec-@@tostringtag)?
With packages that add overrides as a service this is not the best. I'm looking for a scripted way to avoid this. At the moment that's calling `npm update`.
@SukkaW > I wouldn't recommend using npm update Agreed but no other options for folks using `npm`. It's definitely not a _good_ option. **Update:** Hoping this can land soon https://github.com/npm/cli/pull/7025.
@jkrems > @std/esm doesn't allow import w/o mjs by default afaik. But I assume you're talking about the unlockables... I think `@std/esm` is pretty great *(totally biased)*. It's implemented more...