-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
request timed out #215
Comments
is this bug still present? |
I'm getting the same trying to import
Had it with other |
I'm also encountering this. Seems to fail for some packages but works for others. HTTP 408
Works fineLooks like some more heavily used/common packages that are already cached are okay. WorkaroundUse https://cdn.skypack.dev or another similar esm shim provider/cdn. |
Had this output presented to me, after I received a 408 previously. Looks like the CDN has cached the output of the process even though it failed to process the request. You should be able to see the same output by visiting https://esm.sh/react-router-dom/server yarn add react-router-dom@6.0.2: yarn add v1.22.11 info No lockfile found. [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... warning " > react-router-dom@6.0.2" has unmet peer dependency "react@>=16.8". warning " > react-router-dom@6.0.2" has unmet peer dependency "react-dom@>=16.8". warning "react-router-dom > react-router@6.0.2" has unmet peer dependency "react@>=16.8". error Could not write file "/tmp/esm-build-92694869e2404d4459722e05644d3c3e93d6fb6e-4812977b/yarn-error.log": "ENOSPC: no space left on device, open '/tmp/esm-build-92694869e2404d4459722e05644d3c3e93d6fb6e-4812977b/yarn-error.log'" error An unexpected error occurred: "ENOSPC: no space left on device, mkdir '/tmp/esm-build-92694869e2404d4459722e05644d3c3e93d6fb6e-4812977b/node_modules/react-router'". info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command. |
I just released v58, fixed the build cache problem (build task did not delete the cache directory after build randomly that stolen a lot of system storage space). |
Confirmed that issue is resolved/fixed on my end, thanks @ije ! |
@ije thanks for the update, but I'm still having problems importing into Deno. It seems that I can run this project locally and it appears to work fine using |
@samlaycock which package you import? i will look into it |
@ije getting 408 trying to use any of my packages, eg. https://esm.sh/@detachhead/ts-helpers |
I'm getting timeouts with the lastest AJV versions (8.6.3 works for me but it might be cached, 8.7.0+ is broken) |
@separaterecords I just recovered the stable queue used before in c2677ef |
@ije Hey, sorry for the delayed response. My issue was around some dependencies related to |
I'm seeing timeouts for |
As of today, with esm.sh v58, I'm also seeing timeouts for https://esm.sh/preact@10. |
Now it works again, but I briefly saw this while refreshing:
|
Just FYI – I've setup a copy of |
i improved the nodejs service in 65f0b94, which may block the message channel then case the timeout problem |
So far, every package I've tested on esm.sh has worked, so your fix may have indeed fixed the timeouts. I'll keep checking for the next few days and let you know if I see anymore. |
Yup, this fixed everything, thanks @ije. For example, |
The text was updated successfully, but these errors were encountered: