Curtis Man
Curtis Man
@rhuanjl a) yeah.. I don't have a macOS to work thru the build issues. Someone will have to take the change and work on it a bit. b) the existing...
Just FYI, we currently use `node-fetch` v2, which just bind to the browser version of `fetch` in the browser context and should not require the node polyfills. `node-fetch` v3 dropped...
Upgrading to `node-fetch` v3 is possible as long as we add the shim to redirect it to the browser implementation ourselves. I haven't look into cross-fetch, but I believe it...
@RishhiB do you have ADO item tracking this? What's the ETA?
I wonder how to get the maintainer's attention to get contribution merged in?
@tummalasujith, Just to close on this issue: npm semver ^ ranges doesn't consider any prerelease versions unless the version also has a prerelease tag: e.g. ^0.59.4002-0 will match 0.59. where...
URL is the identity of the reference, so having the minimum sequence number that the URL Is valid make sense. It is very likely that changing a URL will render...
I believe the bug is here: https://github.com/electron/asar/blob/4c1a5474266a86ba52872226579a780af7092c7f/src/filesystem.ts#L180 where the symlink target, which could be an absolute path, is joined with the symlink original location's parent path. It should use `path.resolve`...
~~Would it be better to detect if the flag changes and trigger the incremental build by writing those out as an additional separate done file?~~ Actually, what is happening is...