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
{{ message }}
Repository navigation
Typo in importing process in multiple files in lib/internal/streams #526
I was building an app where I imported @toruslabs/base-controllers. The @toruslabs/base-controllers have readable-stream as a dev-dependency as listed in the package.json file.
My node version: v18.14.1
Problem
When I ran my code, it threw the below error. Clearly, the error was because it couldn't find any process/ module as there is no such thing.
The error was fixed when I changed all the process/ to process. As I was checking through the readable-stream repository, I found multiple typos in the process module in the repo. This might be breaking a lot of apps and I think this can be easily fixed with a single PR.
Solution
The typo needs to be fixed in these files 👇
I would love to work on the issue, let me know if I missed something.
Thank You
It's an old trick to tell Node.js (and bundlers that follow the same require() algorithm) to load an npm package instead of a core module.
Might be an issue with Vite specifically. We don't directly test Vite (in dev mode) but we do test Rollup here (which is what Vite uses in production mode):
I'm seeing this issue when trying to use archiver (which includes this project under the hood) when running a vanilla Node.js script on version 20.2.0:
I ran into the same problem when working on an Obsidian plugin. It builds fine but crashes at runtime in the Obsidian electron desktop app because it can't find process/. I'm using esbuild.
Activity
rluvaton commentedon Sep 21, 2023
looking at the history it looks like this was intended:
vweevers commentedon Sep 21, 2023
It's an old trick to tell Node.js (and bundlers that follow the same
require()algorithm) to load an npm package instead of a core module.Might be an issue with Vite specifically. We don't directly test Vite (in dev mode) but we do test Rollup here (which is what Vite uses in production mode):
readable-stream/test/browser/runner-prepare.mjs
Lines 94 to 97 in 268229d
ankitzm commentedon Sep 22, 2023
Ohh, thanks for reviewing @rluvaton and @vweevers.
Will try it using vite in production mode and update here. Thanks.
BryanWallin commentedon Jun 18, 2024
I'm seeing this issue when trying to use
archiver(which includes this project under the hood) when running a vanilla Node.js script on version 20.2.0:It appears the appended
/no longer works in Node.js 20? This is our usage of it:MMesch commentedon Jun 24, 2024
I ran into the same problem when working on an Obsidian plugin. It builds fine but crashes at runtime in the Obsidian electron desktop app because it can't find
process/. I'm using esbuild.https://forum.obsidian.md/t/cant-enable-plugin-depending-on-readable-stream/84235
Not sure how to work around this yet. Looking forward to ideas.
jonluca commentedon Jun 25, 2024
Adding in
processusingyarn add processworked for now with esbuild, but it feels like this is going to break.