Ecosystem Compatibility (2024-02-05 onward)

[kriskowal]

Index of ecosystem compatibility notes from 2021-02-10 to 2024-02-05 #1950 with updates to follow in subsequent comments and separate issues with the label ecosystem-compatibility.

• axios

  • evade override mistake axios/axios#6264

• babel

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)
  • Babel versions circa 7.20 are incompatible with Hardened JavaScript #1846

• buffer

  • 2021-03-06 ses-ava vs install-ses import order matters when it should not. Agoric/agoric-sdk#2663

• chalk

  • ^4
    • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• core-js

  • Array.prototype.push has extra "prototype" property zloirock/core-js#1092

• @cosmjs/types

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• d3

  • 2021-03-03 Fixed Patch vega d3 fix fixme Agoric/agoric-sdk#2575

• enzyme

  • 2021-02-10 Good news about JSS and enzyme chore: add ui-components package Agoric/agoric-sdk#2321 (comment)

• follow-redirects

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• @formatjs/intl-utils

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• gun

  • remove built-in pollution amark/gun#1217

• immerjs

  • fix: compatibility with Secure EcmaScript immerjs/immer#914
  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• jss

  • 2021-02-10 Good news about JSS and enzyme chore: add ui-components package Agoric/agoric-sdk#2321 (comment)

• luxon

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• mobx

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)
    • feat(ses): enablements needed by (old?) mobx #2030

• node

  • Confuses constructor accessor in log messages get rid of <[Object: null prototype] {}> console noise Agoric/agoric-sdk#2324
  • internal/process/per_thread.js is incompatible with Hardened JS shim nodejs/node#43496
  • fix: avoid override by assignment nodejs/node#43907

• node-external-editor

  • Generated TypeScript throws with frozen intrinsics mrkmg/node-external-editor#25

• pino

  • fix: avoid override mistake pinojs/pino#1939

• protobuf

  • fix: update minimal.js to evade override mistake protobufjs/protobuf.js#1742
  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)
  • Support HardenedJS protobufjs/protobuf.js#1713

• react

  • feat: non-security mode for create-react-scripts compat. (KLUDGE) #642
  • failed to delete intrinsics #612
  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• readable-steam

  • Evade override mistake nodejs/readable-stream#474

• reflect-metadata

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• rxjs

  • fix: assignment to function.call web3/web3.js#4918
  • Evade override mistake ReactiveX/rxjs#6991

• regenerator-runtime

  • Compatibility: regenerator-runtime #621
  • runtime - class inheritance pattern not compatible with frozen intrinsics facebook/regenerator#410
  • Runtime - Support frozen intrinsics facebook/regenerator#411

  impacted by use of regnerator-runtime Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

  • @ceramicnetwork/rpc-transport
  • @ceramicstudio/idx
  • @uniswap/v3-sdk
  • key-did-provider-ed25519
  • rpc-utils (before 0.6.0)

• rollup

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• stack-utils

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• tape

  • 2020-09-23 Fear that tape overrode Function.prototype.apply cleared by @ljharb at Should we stop suppressing the override mistake for Function.prototype.apply? #474

• typescript

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)
  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• @wry/context

  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)
  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)
  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)
  • Ecosystem Compatibility Tracking (2021-02-10 to 2024-02-05) #1950 (comment)

• vega

  • 2021-02-10 Fixed chore: add ui-components package Agoric/agoric-sdk#2321 (comment)
  • 2021-03-03 Fixed Patch vega d3 fix fixme Agoric/agoric-sdk#2575
  • Do not override primordial property by assignment vega/vega#3109
  • Vega triggers override mistake when overriding O.p.hasOwnProperty by assignment vega/vega#3075

[naugtur]

TODO: https://github.com/isaacs/minimatch/blob/ef8f2672bdbbf6a632ea815636659fb31b5169aa/src/index.ts#L1012

[gibson042]

TODO: https://github.com/isaacs/minimatch/blob/ef8f2672bdbbf6a632ea815636659fb31b5169aa/src/index.ts#L1012

PR for that is at isaacs/minimatch#228

[kriskowal]

mimic-fn does not compose well with our toString enablements. This manifests as a “Cannot define property with both value and get” (effectively). I have proposed a fix: sindresorhus/mimic-function#51

[ljharb]

wouldn't that fix end up setting writable to false when it's a getter, because there's no writable in the first place? or is that fine

[kriskowal]

wouldn't that fix end up setting writable to false when it's a getter, because there's no writable in the first place? or is that fine

That’s a good question for @sindresorhus and the intended outcome for mimic-function. I think mirroring a getter with a non-writable value is possibly consistent with the intent.

[erights]

See #2033 (comment)

Should #2033 be tracked here as an endo ecosystem compat issue?