Christopher Svanefalk comments

Results 110 comments of


                                            Christopher Svanefalk

Proxy is not working but npm works well

@curio77 @ghostd @fengcen @gdipkf1986 are you guys by any chance on Windows as well? Starting to suspect this is an OS specific issue.

Proxy is not working but npm works well

FWIW we eventually solved this by not giving yarn any proxy config settings at all, but only using the `proxy` and `https_proxy` system variables. Works fine, though I have no...

Xvfb is completely ruining my life and job.

FWIW I *think* I solved this on a CentOS 8 box by spinning up the xvfb server externally: ``` /usr/bin/Xvfb :99 -screen 0 1920x1080x24+32 & export DISPLAY=:99 ``` At any...

Replace `@cypress/request`

Regarding potential replacements, would not the native `fetch` API be considered a stable replacement for `request`?

[Package Request] - Node v22 and v24

Node 23 is now out, and 22 will enter Current LTS status by end of this month. It is extremely relevant to have it added as an official package. https://openjsf.org/blog/announcing-node.js-23-key-features-and-enhancement

[Package Request] - Node v22 and v24

Node 22.11.0 is the current LTS now and 20 will eventually be phased out. Having 22 as an official package would be great!

[Package Request] - Node v22 and v24

Node 22 has now been the current LTS for almost half a year. Would it be possible to get some indication of where on the AL roadmap this is?

[Package Request] - Node v22 and v24

FYI Node 24 is now officially the latest LTS https://github.com/nodejs/node/releases/tag/v24.11.0

`vm.compileFunction(source)` is much slower than `new vm.Script(source)`

This is huge @joyeecheung ,thank you so much ❤️

How to deal with refresh tokens?

You can memoize the connection URL based on the token ``` const accessToken = useToken(); const socketURL = useMemo(() => `${apiPath}/?token=${accessToken}`); const socket = useReactWebSocket(socketURL); ```