You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason my dep bot auto merged a failing build of streaming iterables with the v0.1.14 release. Since then I get a "Something strange happened" (logs). I tossed in some console logs and it seems to coming from my batch module which has something that is no longer supported. And the change in 0.1.14 that is throwing seems to be here.
You can test the failure by cloning this commit and running npm build or node bundle-types.mjs.
Happy to debug, but I'm off to enable branch protection.
The text was updated successfully, but these errors were encountered:
reconbot
added a commit
to reconbot/streaming-iterables
that referenced
this issue
Sep 9, 2023
A strange datapoint - when debugging with streaming iterables, I accidentally installed pnpm and the build passed. As of this commit an npm install fails (via build script of node bundle-types.mjs) and a pnpm install succeeds.
For some reason my dep bot auto merged a failing build of streaming iterables with the v0.1.14 release. Since then I get a "Something strange happened" (logs). I tossed in some console logs and it seems to coming from my
batch
module which has something that is no longer supported. And the change in 0.1.14 that is throwing seems to be here.You can test the failure by cloning this commit and running
npm build
ornode bundle-types.mjs
.Happy to debug, but I'm off to enable branch protection.
The text was updated successfully, but these errors were encountered: