-
Notifications
You must be signed in to change notification settings - Fork 0
migrate to cloudflare services #3
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
base: creation
Are you sure you want to change the base?
Conversation
Deploying with
|
Latest commit: |
427fc0a
|
Status: | ✅ Deploy successful! |
Preview URL: | https://bd8756d3.jspm-packages.pages.dev |
I'm still getting 1s on cold loads - I wonder if workers are faster? It's all well and good to use the latest hype, but over 500ms for a page request is too slow. |
would you suggest something else? I can try other solutions. |
const NPM_PROVIDER_URL = "https://ga.jspm.io/npm:"; | ||
const packageName = params.package.join("/"); | ||
const baseURL = `${NPM_PROVIDER_URL}${packageName}`; | ||
const jspmPackage = await fetch( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you do this fetch in parallel with the readme fetch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried it here, see if this is what you suggested.
Can be tested at this URL
https://3059f0a9.jspm-packages.pages.dev/package/es-module-shims@1.3.5
I don't think Rust would result in any performance benefit - if anything it increases the startup time, unless there is an actual computation bottleneck. Rather we just need to find an edge that is close to Amazon cloudfront. Possibly comparing Amazon lambda might be another option. |
Deploy as a single edge function with objective of ~50ms SSR response.