-
Notifications
You must be signed in to change notification settings - Fork 389
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
fix: live tunnel arch issue #4064
Conversation
📊 Benchmark resultsComparing with 7ec8cdc Package size: 355 MB⬆️ 0.00% increase vs. 7ec8cdc
Legend
|
src/lib/exec-fetcher.js
Outdated
@@ -1,13 +1,15 @@ | |||
// @ts-check | |||
const path = require('path') | |||
const process = require('process') | |||
const { stringify } = require('querystring') |
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.
[sand] What are your thoughts on using new URL()
and url.searchParams.set()
instead?
This is mostly equivalent, except it uses the DOM API instead of Node.js core API. What are your thoughts on this?
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.
Yea why not I don't have a preference to be honest -> is there any benefit?
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.
If we had more code to share with the front-end, it would be better. And Node.js has been moving in that direction lately of using more and more the DOM API, as opposed to to its own core Node.js modules (URI
, AbortSignal
, EventTarget
, globalThis
, ES modules, Blob
, ReadableStream
/WritableStream
/TransformStream
, Worker
, Web Crypto, performance
, structuredClone
), which seems a good thing at a higher level, and is also closer to the direction Deno is heading.
However, this is more of a conceptual benefit in this case, since we do not intend to run this file anywhere but on a terminal in this case, so either way could work. 👍
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 just realized this too: querystring
is marked as "legacy" in the Node.js documentation.
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'll change it for you ;)
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.
This looks good to me.
I'll @ehmicky and @lukasholzer resolve https://github.com/netlify/cli/pull/4064/files#r786137881
https://github.com/netlify/cli/pull/4064/files#r786137881 was more of a side note, please feel free to dismiss! :) |
@erezrokah who is the best one to review the matching PR in the live tunnel repo? netlify/live-tunnel#112 |
just tried the new binary for arm64 on my m1 mac and it works 🥳 |
@charliegerard I hope it works now on the raspberry pi ;) I added now following CPU architectures: https://github.com/netlify/live-tunnel-client/releases/tag/v0.2.10 |
omg thank you so much for working on it!! 😃 🙌 Right on time for a talk I have to give next week 🥳 I'll test it a bit later today! |
🎉 Thanks for submitting a pull request! 🎉
Summary
Fixes #3561
This will now stop working for debian arm64 so we need to build the image first before merging.
The matching PR for cross compiling the different CPU architectures https://github.com/netlify/live-tunnel/pull/112
For us to review and ship your PR efficiently, please perform the following steps:
passes our tests.
A picture of a cute animal (not mandatory, but encouraged)