-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with module resolution loading sharp
native module as dependency via npm:
specifier
#16578
Comments
cd ~/Library/Caches/deno/npm/registry.npmjs.org/sharp/0.31.2
npm i deno run --unstable --allow-read --allow-env --allow-ffi index.ts
|
@k-right It seems like a recent bug in Sharp: lovell/sharp#3438 |
@littledivy Yep, looks like it. Tried same strategies with Docker Without
|
Seems this is the same problem as #17085 |
@k-right it seems this example involves several other packages. Could you try to boil it down into two separate issues - one for |
I've seen the sharp error happen on old versions of Mac OS's. I know nothing about deno but just wanted to put that out there in case it helps you guys narrow down what the problem is. |
|
I tried while checking When all binary files are in place, |
@zwn by "when all binary files are in place" do you mean that you manually run postinstall script? |
@bartlomieju I just tried to import There were two parts to make it working:
|
facing same issue.
|
This issue specific to sharp can be closed since sharp v0.33. |
Trying to get
payload
running on Deno unstable. Module resolution seems to get confused on thesharp
module (specifically loading its native component).Minimal example to reproduce:
The text was updated successfully, but these errors were encountered: