Giter VIP home page Giter VIP logo

httptoolkit-ui's Introduction

HTTP Toolkit UI Build Status

This repo contains the UI for HTTP Toolkit, a beautiful, cross-platform & open-source HTTP(S) debugging proxy, analyzer & client.

Looking to file bugs, request features or send feedback? File an issue or vote on existing ones at github.com/httptoolkit/httptoolkit.

What is this?

HTTP Toolkit is built as a single-page web application (this repo), running on top of a server that provides access to non-web functionality (e.g. running a proxy server), typically run through an electron desktop wrapper app. The core UI and the majority of HTTP Toolkit functionality all lives here, except for desktop-app specific behaviour & build configuration, or functionality that can't be implemented in a web app.

The UI is built as a TypeScript React app, using MobX for state and Styled Components for styling, with Mockttp used to manage the HTTP interception itself.

When running, the UI is typically used via app.httptoolkit.tech, even in the desktop app (it's not embedded there, but hosted standalone). It can either be used through the desktop app (which starts its own server), or users can start their own server and open the UI in a browser directly.

Contributing

If you want to change the behaviour of the HTTP Toolkit in almost any way, except the low-level HTTP handling (see Mockttp), how interceptors start applications (see httptoolkit-server) or how it's packaged and distributed (see httptoolkit-desktop), then you're in the right place 👍.

To get started:

  • Clone this repo.
  • npm install
  • For pure UI development
  • To develop the UI & server together
    • Start a server locally
    • Run npm run start:web to start the UI without running a separate HTTP Toolkit server
    • Open localhost:8080 to view the UI
  • npm test - run the tests (not many yet, but more are very welcome!)

httptoolkit-ui's People

Contributors

aluasm avatar bleuzen avatar datenreisender avatar dependabot[bot] avatar lord-ne avatar mitchcapper avatar pimterry avatar roschaefer avatar shirshak55 avatar starmania avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

httptoolkit-ui's Issues

Fonts fetch failures

Running ui locally using npm run start:web. Constantly failing to fetch font urls such as https://gwfh.mranftl.com/api/fonts, https://gwfh.mranftl.com/api/fonts/lato?subsets=latin.

This results in Uncaught Exceptions.

httptoolkit-ui/node_modules/node-fetch/lib/index.js:1491
			reject(new FetchError(`request to ${request.url} failed, reason: ${err.message}`, 'system', err));

FetchError: request to https://gwfh.mranftl.com/api/fonts failed, reason: 
    at ClientRequest.<anonymous> (httptoolkit-ui/node_modules/node-fetch/lib/index.js:1491:11)
    at ClientRequest.emit (node:events:518:28)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:518:28)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at listOnTimeout (node:internal/timers:540:9)
    at processTimers (node:internal/timers:514:7)

Possibly network issues on my end.
However, is it worthwhile/possible to have the fonts downloaded locally and local content is accessed if there is a failure in URL fetch?

[ Suggestion ] Add cookies search filters.

My suggestion as you can see from its title is very simple.
I want you do add "cookies" and "set-cookies" filters to the search feature.
So it will be easier to monitor cookie changes

HAR: Inconsistent application/octet-stream post request payloads when exporting exchanges as http archive

HTTPToolkit assumes all post request contents are valid UTF-8 while exporting HTTP Archive (HAR) exchanges, ignoring the presence of Content-Type: application/octet-stream headers in the process.

For example, the following binary request payload 0xa4, 0x26, 0x37, 0x13, 0x35, 0xe7, 0x50, 0x27 will fail to decode as valid UTF-8 (when reaching this constructor), and will instead transform into [0xef, 0xbf, 0xbd], 0x26, 0x37, 0x13, 0x35, [0xef, 0xbf, 0xbd], 0x50, 0x27, group [0xef, 0xbf, 0xbd] being the UTF-8 equivalent of Unicode U+FFFD, replacement character

Here's a demonstration:
image

Although this in it's own, can be delegated as an issue mainly affecting the HTTP Archive 1.2 spec, it is worth noting that HTTPToolkit actively mitigates this on the Response constructor equivalent, albeit, to an unknown extent.

There's been proposals on implementing an additional "encoding" field in HTTP Archive 1.3 spec, which could allow for safer handling of post request raw binary payloads, however, I was not able to find any libraries handling this out of the box. That being said, a possible temporary workaround would be to base64 encode any application/octet-stream request payload, and allow end users to work with the encoded data accordingly.

Lastly, thank you for releasing and open-sourcing such an awesome tool to the community, HTTPToolkit has been extremely helpful so far, and I look forward to finding out what interesting capabilities further development will bring.


Does this affect you too? Click the +:smiley: icon in the top right and add a :+1: on issues to help decide where HTTP Toolkit goes next, or go take a look & vote on the most popular ideas so far.

Support latest npm?

NPM Version: 8.1.0

Currently, we seem to have a lot of issues on the latest npm so maybe attempt to fix it?

npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: Deprecated due to CVE-2021-21366 resolved in 0.5.0
npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated [email protected]: This package has been renamed to @vscode/emmet-helper, please update to the new name
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated [email protected]: 3.x is no longer supported
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Removed event-stream from gulp-header
npm WARN deprecated [email protected]: Fixed a prototype pollution security issue in 4.1.0, please upgrade to ^4.1.1 or ^5.0.1.
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated @types/[email protected]: This is a stub types definition for react-ga (https://github.com/react-ga/react-ga). react-ga provides its own type definitions, so you don't need @types/react-ga installed!
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/pinpoint'
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/formula'
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address'
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Please update to the latest object-keys
npm WARN deprecated [email protected]: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code E401
npm ERR! Incorrect or missing password.
npm ERR! If you were trying to login, change your password, create an
npm ERR! authentication token or enable two-factor authentication then
npm ERR! that means you likely typed your password in incorrectly.
npm ERR! Please try again, or recover your password at:
npm ERR!     https://www.npmjs.com/forgot
npm ERR! 
npm ERR! If you were doing some other operation then your saved credentials are
npm ERR! probably out of date. To correct this please try logging in again with:
npm ERR!     npm login

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/quantum/.npm/_logs/2021-10-30T09_52_07_428Z-debug.log

From the log file

9707 verbose stack HttpErrorAuthUnknown: Unable to authenticate, need: Basic realm="https://npm.fontawesome.com/",service="npm.fontawesome.com"
9707 verbose stack     at /home/quantum/.fnm/node-versions/v17.0.1/installation/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:84:17
9707 verbose stack     at runMicrotasks (<anonymous>)
9707 verbose stack     at processTicksAndRejections (node:internal/process/task_queues:96:5)
9708 verbose statusCode 401
9709 verbose pkgid @fortawesome/react-fontawesome@https://npm.fontawesome.com/@fortawesome/react-fontawesome/-/0.1.8/react-fontawesome-0.1.8.tgz
9710 verbose cwd /home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui
9711 verbose Linux 5.13.0-7614-generic
9712 verbose argv "/home/quantum/.fnm/node-versions/v17.0.1/installation/bin/node" "/tmp/fnm_multishells/4899_1635587382443/bin/npm" "install"
9713 verbose node v17.0.1
9714 verbose npm  v8.1.0
9715 error code E401
9716 error Incorrect or missing password.
9717 error If you were trying to login, change your password, create an
9717 error authentication token or enable two-factor authentication then
9717 error that means you likely typed your password in incorrectly.
9717 error Please try again, or recover your password at:
9717 error     https://www.npmjs.com/forgot
9717 error
9717 error If you were doing some other operation then your saved credentials are
9717 error probably out of date. To correct this please try logging in again with:
9717 error     npm login
9718 verbose exit 1

`npm start` doesn't work on Windows

I was trying to compile/run this repo following the instructions in the README, but I'm getting a lot of errors that I'm not sure how to deal with. I'm not sure exactly what I'm doing wrong.

I'm on Windows. I cloned the repo and ran npm install.

Running npm start yields:

> [email protected] start
> ./node_modules/httptoolkit-server/bin/run start & npm run start:web

'.' is not recognized as an internal or external command,
operable program or batch file.

> [email protected] start:web
> env-cmd -f ./automation/ts-node.env webpack-dev-server --config ./automation/webpack.dev.ts

i 「wds」: Project is running at http://local.httptoolkit.tech:8080/
i 「wds」: webpack output is served from /
i 「wds」: Content not from webpack is served from C:\Users\Noam\Desktop\httptoolkit-ui-master\dist
i 「wds」: 404s will fallback to /index.html
i 「wdm」: Hash: 9685bf8b84bc1511f2ab
Version: webpack 4.46.0
Time: 33958ms
Built at: 11/08/2022 3:27:59 PM
i 「wdm」: Compiled successfully.
No issues found.

When opening the actual local.httptoolkit.tech:8080 site in the browser (Firefox), it displays the "This is taking longer than normal" message, and a whole bunch and a bunch of errors appear in the console, including the following:

Error messages
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS request did not succeed). Status code: (null).
proxy-store.ts:55
Server initialization failed TypeError: NetworkError when attempting to fetch resource.
index.tsx:66
Service worker not supported, oh well, no autoupdating for you.
index.tsx:129
Previous server version was null
errors.ts:55
Reporting error: Error: Failed to initialize application
    <anonymous> index.tsx:131
    fulfilled index.tsx:31
    promise callback*step index.tsx:33
    __awaiter index.tsx:34
    __awaiter index.tsx:30
    <anonymous> index.tsx:128
    promise callback* index.tsx:128
    tsx app.js:27449
    __webpack_require__ app.js:105
    0 app.js:28277
    __webpack_require__ app.js:105
    <anonymous> app.js:275
    <anonymous> app.js:278

So it seems like the server isn't being run because of the first error, and I would then assume that all of the browser console errors are because the server isn't running. The error '.' is not recognized as an internal or external command, operable program or batch file. seems to indicate that this repo isn't set up to be run on Windows. Do I need to develop on Linux?

Cannot build on Windows 11

I was trying to compile and run httptoolkit-ui following the instructions in the README, but npm install gives me build errors. I tried to investigate the issue and found that it is due to a dependency win-version-info which uses deprecated C++ features according to this.

Here is the terminal output:-

npm WARN deprecated @types/[email protected]: This is a stub types definition. classnames provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/pinpoint'
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: Removed event-stream from gulp-header
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/formula'
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated [email protected]: 3.x is no longer supported
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address'
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: This package has been renamed to @vscode/emmet-helper, please update to the new name
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'
npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated [email protected]: Please upgrade to v7.0.2+ of superagent.  We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing.  See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>. Thanks to @shadowgate15, @spence-s, and @niftylettuce. Superagent is sponsored by Forward Email at <https://forwardemail.net>.
npm WARN deprecated [email protected]: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated [email protected]: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN cleanup Failed to remove some directories [
npm WARN cleanup   [
npm WARN cleanup     'D:\\httptoolkit-ui\\node_modules\\node-datachannel',
npm WARN cleanup     [Error: EBUSY: resource busy or locked, rmdir 'D:\httptoolkit-ui\node_modules\node-datachannel'] {
npm WARN cleanup       errno: -4082,
npm WARN cleanup       code: 'EBUSY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: 'D:\\httptoolkit-ui\\node_modules\\node-datachannel'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     'D:\\httptoolkit-ui\\node_modules\\registry-js',
npm WARN cleanup     [Error: EBUSY: resource busy or locked, rmdir 'D:\httptoolkit-ui\node_modules\registry-js'] {
npm WARN cleanup       errno: -4082,
npm WARN cleanup       code: 'EBUSY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: 'D:\\httptoolkit-ui\\node_modules\\registry-js'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     'D:\\httptoolkit-ui\\node_modules\\puppeteer',
npm WARN cleanup     [Error: EBUSY: resource busy or locked, rmdir 'D:\httptoolkit-ui\node_modules\puppeteer'] {
npm WARN cleanup       errno: -4082,
npm WARN cleanup       code: 'EBUSY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: 'D:\\httptoolkit-ui\\node_modules\\puppeteer'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     'D:\\httptoolkit-ui\\node_modules\\ssh2',
npm WARN cleanup     [Error: EPERM: operation not permitted, rmdir 'D:\httptoolkit-ui\node_modules\ssh2\lib\protocol\crypto\build\Release\obj'] {
npm WARN cleanup       errno: -4048,
npm WARN cleanup       code: 'EPERM',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: 'D:\\httptoolkit-ui\\node_modules\\ssh2\\lib\\protocol\\crypto\\build\\Release\\obj'
npm WARN cleanup     }
npm WARN cleanup   ]
npm WARN cleanup ]
npm ERR! code 1
npm ERR! path D:\httptoolkit-ui\node_modules\win-version-info
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node skip.js || prebuild-install || node-gyp rebuild
npm ERR! Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.
npm ERR!   VersionInfo.cc
npm ERR! D:\httptoolkit-ui\node_modules\nan\nan.h(2544,6): warning C4996: 'v8::ObjectTemplate::SetAccessor': Do signature check in accessor [D:\httptoolkit-ui\node_modules\win-version-info\build\VersionInfo.vcxproj]
npm ERR!   showver.cc
npm ERR! D:\httptoolkit-ui\node_modules\nan\nan.h(2544,6): warning C4996: 'v8::ObjectTemplate::SetAccessor': Do signature check in accessor [D:\httptoolkit-ui\node_modules\win-version-info\build\VersionInfo.vcxproj]
npm ERR! D:\httptoolkit-ui\node_modules\win-version-info\src\showver.cc(111,70): error C2039: 'ptr_fun': is not a member of 'std' [D:\httptoolkit-ui\node_modules\win-version-info\build\VersionInfo.vcxproj]
npm ERR! C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\include\locale(25): message : see declaration of 'std' [D:\httptoolkit-ui\node_modules\win-version-info\build\VersionInfo.vcxproj]
npm ERR! D:\httptoolkit-ui\node_modules\win-version-info\src\showver.cc(111,77): error C2065: 'ptr_fun': undeclared identifier [D:\httptoolkit-ui\node_modules\win-version-info\build\VersionInfo.vcxproj]
npm ERR! D:\httptoolkit-ui\node_modules\win-version-info\src\showver.cc(111,78): error C2062: type 'int' unexpected [D:\httptoolkit-ui\node_modules\win-version-info\build\VersionInfo.vcxproj]
npm ERR! D:\httptoolkit-ui\node_modules\win-version-info\src\showver.cc(115,61): error C2039: 'ptr_fun': is not a member of 'std' [D:\httptoolkit-ui\node_modules\win-version-info\build\VersionInfo.vcxproj]
npm ERR! C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\include\locale(25): message : see declaration of 'std' [D:\httptoolkit-ui\node_modules\win-version-info\build\VersionInfo.vcxproj]
npm ERR! D:\httptoolkit-ui\node_modules\win-version-info\src\showver.cc(115,68): error C2065: 'ptr_fun': undeclared identifier [D:\httptoolkit-ui\node_modules\win-version-info\build\VersionInfo.vcxproj]
npm ERR! D:\httptoolkit-ui\node_modules\win-version-info\src\showver.cc(115,69): error C2062: type 'int' unexpected [D:\httptoolkit-ui\node_modules\win-version-info\build\VersionInfo.vcxproj]
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | win32 | x64
npm ERR! gyp info find Python using Python version 3.11.2 found at "C:\Users\itsyourap\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\python.exe"
npm ERR! gyp info find VS using VS2019 (16.11.33328.57) found at:
npm ERR! gyp info find VS "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools"
npm ERR! gyp info find VS run with --verbose for detailed information
npm ERR! gyp info spawn C:\Users\itsyourap\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\python.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   'C:\\Users\\itsyourap\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\gyp\\gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'msvs',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'D:\\httptoolkit-ui\\node_modules\\win-version-info\\build\\config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'C:\\Users\\itsyourap\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   'C:\\Users\\itsyourap\\AppData\\Local\\node-gyp\\Cache\\18.14.2\\include\\node\\common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=C:\\Users\\itsyourap\\AppData\\Local\\node-gyp\\Cache\\18.14.2',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=C:\\Users\\itsyourap\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=C:\\\\Users\\\\itsyourap\\\\AppData\\\\Local\\\\node-gyp\\\\Cache\\\\18.14.2\\\\<(target_arch)\\\\node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=D:\\httptoolkit-ui\\node_modules\\win-version-info',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'D:\\httptoolkit-ui\\node_modules\\win-version-info\\build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\MSBuild.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   'build/binding.sln',
npm ERR! gyp info spawn args   '/clp:Verbosity=minimal',
npm ERR! gyp info spawn args   '/nologo',
npm ERR! gyp info spawn args   '/p:Configuration=Release;Platform=x64'
npm ERR! gyp info spawn args ]
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\MSBuild.exe` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onExit (C:\Users\itsyourap\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:203:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Windows_NT 10.0.22621
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\itsyourap\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd D:\httptoolkit-ui\node_modules\win-version-info
npm ERR! gyp ERR! node -v v18.14.2
npm ERR! gyp ERR! node-gyp -v v9.3.1
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\itsyourap\AppData\Local\npm-cache\_logs\2023-03-04T09_12_17_474Z-debug-0.log

2023-03-04T09_12_17_474Z-debug-0.log

> npm --version
9.5.1
> node --version
v18.14.2

How do I fix these errors and compile this?
Thanks in advance

centos7 npm install error

centos7 My nodejs version is 20.11.1 npm config set registry https://registry.npmmirror.com/
Then there was an error in npm install
[root@ecs-92a4 httptoolkit-ui-main]# npm install
npm WARN deprecated @types/[email protected]: This is a stub types definition. classnames provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated [email protected]: Removed event-stream from gulp-header
npm WARN deprecated [email protected]: Use String.prototype.trim() instead
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: This package has been renamed to @vscode/emmet-helper, please update to the new name
npm WARN deprecated [email protected]: < 21.5.0 is no longer supported
npm WARN deprecated [email protected]: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated [email protected]: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 2
npm ERR! path /app/red-booklet/httptoolkit/httptoolkit-ui-main/node_modules/node-datachannel
npm ERR! command failed
npm ERR! command sh -c prebuild-install || (npm install --ignore-scripts --production=false && npm run _prebuild)
npm ERR! added 598 packages, and removed 1 package in 9s
npm ERR!
npm ERR! 7 packages are looking for funding
npm ERR! run npm fund for details
npm ERR!
npm ERR! > [email protected] _prebuild
npm ERR! > prebuild --backend cmake-js
npm ERR!
npm ERR! [
npm ERR! '/root/.nvm/versions/node/v20.11.1/bin/node',
npm ERR! '/app/red-booklet/httptoolkit/httptoolkit-ui-main/node_modules/node-datachannel/node_modules/.bin/cmake-js',
npm ERR! 'rebuild',
npm ERR! '--runtime-version=20.11.1',
npm ERR! '--arch=x64',
npm ERR! '--runtime=node'
npm ERR! ]
npm ERR! prebuild-install WARN install Request timed out
npm ERR! npm WARN config production Use --omit=dev instead.
npm ERR! npm WARN deprecated [email protected]: this library is no longer supported
npm ERR! npm WARN deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm ERR! npm WARN deprecated [email protected]: Use your platform's native DOMException instead
npm ERR! npm WARN deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin.
npm ERR! npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm ERR! npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm ERR! npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm ERR! npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm ERR! prebuild info begin Prebuild version 11.0.4
npm ERR! prebuild info build Preparing to prebuild [email protected] for node 20.11.1 on linux-x64 using cmake-js
npm ERR! info TOOL Using Unix Makefiles generator.
npm ERR! ERR! OMG CMake executable is not found. Please use your system's package manager to install it, or you can get installers from there: http://cmake.org.
npm ERR! prebuild ERR! build Error: Failed to build cmake with exit code 1
npm ERR! prebuild ERR! build at ChildProcess. (/app/red-booklet/httptoolkit/httptoolkit-ui-main/node_modules/node-datachannel/node_modules/prebuild/cmakebuild.js:32:19)
npm ERR! prebuild ERR! build at ChildProcess.emit (node:events:518:28)
npm ERR! prebuild ERR! build at ChildProcess._handle.onexit (node:internal/child_process:294:12)

1711797418105

Unable to build in Mac Arm

npm install
npm WARN deprecated @types/[email protected]: This is a stub types definition. classnames provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: Removed event-stream from gulp-header
npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated [email protected]: The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: 0.x is no longer supported. Please upgrade to 3.x or higher.
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Deprecated in favor of https://github.com/styled-components/typescript-styled-plugin
npm WARN deprecated [email protected]: It is not compatible with newer versions of GA starting with v4, as long as you are using GAv3 it should be ok, but the package is not longer being maintained
npm WARN deprecated [email protected]: This package has been renamed to @vscode/emmet-helper, please update to the new name
npm WARN deprecated [email protected]: 3.x is no longer supported. Please upgrade to 6.x or higher.
npm WARN deprecated [email protected]: Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated [email protected]: 16.1.1
npm WARN deprecated @types/[email protected]: This is a stub types definition. yaml provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: < 21.5.0 is no longer supported
npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: 1.x is no longer supported. Please upgrade to 4.x or higher.
npm WARN deprecated [email protected]: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated [email protected]: Use String.prototype.trim() instead
npm WARN cleanup Failed to remove some directories [
npm WARN cleanup   [
npm WARN cleanup     '/Users/macbook/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/karma/node_modules/fsevents',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/Users/macbook/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/karma/node_modules/fsevents'] {
npm WARN cleanup       errno: -66,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/Users/macbook/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/karma/node_modules/fsevents'
npm WARN cleanup     }
npm WARN cleanup   ]
npm WARN cleanup ]
npm ERR! code 1
npm ERR! path /Users/macbook/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/puppeteer
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! The chromium binary is not available for arm64:
npm ERR! If you are on Ubuntu, you can install with:
npm ERR!
npm ERR!  apt-get install chromium-browser
npm ERR!
npm ERR! /Users/macbook/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js:112
npm ERR!             throw new Error();
npm ERR!             ^
npm ERR!
npm ERR! Error
npm ERR!     at /Users/macbook/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js:112:19
npm ERR!     at FSReqCallback.oncomplete (node:fs:199:21)
npm ERR!
npm ERR! Node.js v20.10.0

npm ERR! A complete log of this run can be found in: /Users/macbook/.npm/_logs/2024-02-18T23_31_10_897Z-debug-0.log

I think we can use playwright instead of puppeteer and seems to be well maintained.

Had to go to 0.0.0.0:8080 since the local subdomain isn't by default setup on Linux

Just extracting this out as a separate issue:

OT: But I had to go to the webserver using 0.0.0.0:8080 since the local subdomain isn't by default setup on Linux, is that something the dev has on their computer ?

Originally posted by @stuaxo in #93 (comment)

Can you explain more detail about what you mean by this @stuaxo?

The normal URL you want to use is http://local.httptoolkit.tech:8080 which is a public DNS record, it shouldn't require local configuration - it's just a DNS record that resolves to 127.0.0.1.

It's only better than localhost in that it avoids some restrictions from Auth0 (and some other components I think) around using localhost addresses for local login - you should also be able to just use localhost:8080 if you like, really the only big issue is that login won't work correctly.

Local build is broken

On a fresh checkout I get a lot of deprecation and vulnerability warnings and startup fails.

Unfortunately I don’t have sufficient node experience to fix this myself, looks like a lot of things are outdated / broken, most notably probably the codebase needs to be updated for a more recent webpack version.

$ npm install
npm WARN deprecated @types/[email protected]: This is a stub types definition. classnames provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated [email protected]: Removed event-stream from gulp-header
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/pinpoint'
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/formula'
npm WARN deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: 3.x is no longer supported
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address'
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: This package has been renamed to @vscode/emmet-helper, please update to the new name
npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'
npm WARN deprecated [email protected]: Please upgrade to v7.0.2+ of superagent.  We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing.  See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>. Thanks to @shadowgate15, @spence-s, and @niftylettuce. Superagent is sponsored by Forward Email at <https://forwardemail.net>.
npm WARN deprecated [email protected]: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated [email protected]: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

added 1874 packages, and audited 1933 packages in 3m

134 packages are looking for funding
  run `npm fund` for details

65 vulnerabilities (3 low, 22 moderate, 28 high, 12 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
$ npm run start:web

> [email protected] start:web
> env-cmd -f ./automation/ts-node.env webpack-dev-server --config ./automation/webpack.dev.ts

ℹ 「wds」: Project is running at http://local.httptoolkit.tech:8080/
ℹ 「wds」: webpack output is served from /
ℹ 「wds」: Content not from webpack is served from /tmp/httpui/dist
ℹ 「wds」: 404s will fallback to /index.html
Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/tmp/httpui/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/tmp/httpui/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/tmp/httpui/node_modules/webpack/lib/NormalModule.js:471:10)
    at /tmp/httpui/node_modules/webpack/lib/NormalModule.js:503:5
    at /tmp/httpui/node_modules/webpack/lib/NormalModule.js:358:12
    at /tmp/httpui/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/tmp/httpui/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at iterateNormalLoaders (/tmp/httpui/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
    at /tmp/httpui/node_modules/loader-runner/lib/LoaderRunner.js:236:3
    at runSyncOrAsync (/tmp/httpui/node_modules/loader-runner/lib/LoaderRunner.js:130:11)
    at iterateNormalLoaders (/tmp/httpui/node_modules/loader-runner/lib/LoaderRunner.js:232:2)
    at Array.<anonymous> (/tmp/httpui/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
    at Storage.finished (/tmp/httpui/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
    at /tmp/httpui/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9
Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/tmp/httpui/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/tmp/httpui/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/tmp/httpui/node_modules/webpack/lib/NormalModule.js:471:10)
    at /tmp/httpui/node_modules/webpack/lib/NormalModule.js:503:5
    at /tmp/httpui/node_modules/webpack/lib/NormalModule.js:358:12
    at /tmp/httpui/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/tmp/httpui/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at Array.<anonymous> (/tmp/httpui/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
    at Storage.finished (/tmp/httpui/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
    at /tmp/httpui/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9
    at /tmp/httpui/node_modules/graceful-fs/graceful-fs.js:123:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3)
ode:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

RpcIpcMessagePortClosedError: Cannot send the message - the message port has been closed for the process 1291964.
    at /tmp/httpui/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:47:47
    at process.processTicksAndRejections (node:internal/process/task_queues:81:21) {
  code: undefined,
  signal: undefined
}

Doesn't work with latest npm v17?

httptoolkit-ui via  v17.0.1 took 39s ➜  npm start  

> [email protected] start
> node-dev ./node_modules/httptoolkit-server/bin/run start & npm run start:web


> [email protected] start:web
> env-cmd -f ./automation/ts-node.env webpack-dev-server --config ./automation/webpack.dev.ts

(node:81713) [DEP0125] DeprecationWarning: The _stream_wrap module is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)
Config checked in 9 ms
Certificates setup in 3 ms
Standalone server started in 6 ms
Server started in 12 ms
Total startup took 30 ms
ℹ 「wds」: Project is running at http://local.httptoolkit.tech:8080/
ℹ 「wds」: webpack output is served from /
ℹ 「wds」: Content not from webpack is served from /home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/dist
ℹ 「wds」: 404s will fallback to /index.html
Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:67:19)
    at Object.createHash (node:crypto:130:10)
    at module.exports (/home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/webpack/lib/NormalModule.js:471:10)
    at /home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/webpack/lib/NormalModule.js:503:5
    at /home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/webpack/lib/NormalModule.js:358:12
    at /home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at Array.<anonymous> (/home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
    at Storage.finished (/home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/webpack/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
    at /home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/webpack/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9
    at /home/quantum/Desktop/projects/httptoolkit/httptoolkit-ui/node_modules/graceful-fs/graceful-fs.js:123:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3)

I guess it is some OpenSSL issue. I do have a workaround like setting env variable but it might be better if we fix it?

export NODE_OPTIONS=--openssl-legacy-provider

Error: listen EADDRINUSE

Hello, so im using node v16 and py 3.9. i already build the server and ui. when i want to start both of them it says

PS C:\httptoolkit\httptoolkit-ui> npm start

[email protected] start
npm-run-all --parallel --print-label start:server start:web

[start:web ]
[start:web ] > [email protected] start:web
[start:web ] > env-cmd -f ./automation/ts-node.env webpack-dev-server --config ./automation/webpack.dev.ts
[start:web ]
[start:server]
[start:server] > [email protected] start:server
[start:server] > node ./node_modules/httptoolkit-server/bin/run start
[start:server]
[start:server] Config checked in 38 ms
[start:server] Certificates setup in 19 ms
[start:server] Error: listen EADDRINUSE: address already in use 127.0.0.1:45456
[start:server] at Server.setupListenHandle [as _listen2] (node:net:1463:16)
[start:server] at listenInCluster (node:net:1511:12)
[start:server] at doListen (node:net:1660:7)
[start:server] at processTicksAndRejections (node:internal/process/task_queues:84:21) {
[start:server] code: 'EADDRINUSE',
[start:server] errno: -4091,
[start:server] syscall: 'listen',
[start:server] address: '127.0.0.1',
[start:server] port: 45456
[start:server] }
[start:server] Error: listen EADDRINUSE: address already in use 127.0.0.1:45456
[start:server] Code: EADDRINUSE

Thank you

CORS related error

I'm getting a CORS Related errors on my web browser while trying to access the UI locally. Using https://app.httptoolkit.tech/ works just fine tough.

root@s1:~/httptoolkit# npm run start:web

> start:web
> env-cmd -f ./automation/ts-node.env.js webpack-dev-server --config ./automation/webpack.dev.ts
ℹ 「wds」: Project is running at http://local.httptoolkit.tech:8080/
ℹ 「wds」: webpack output is served from /
ℹ 「wds」: Content not from webpack is served from /root/httptoolkit/dist
ℹ 「wds」: 404s will fallback to /index.html
ℹ 「wdm」: Hash: 9c8fdf9a536133d90353
Version: webpack 4.46.0
Time: 26221ms
Built at: 08/10/2023 16:59:22
ℹ 「wdm」: Compiled successfully.
No issues found.

Here's what I saw from the console log on my browser when trying to open http://local.httptoolkit.tech:8080/:


> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 204.
> 
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS request did not succeed). Status code: (null).
> 
> Server initialization failed TypeError: NetworkError when attempting to fetch resource. proxy-store.ts:55
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 204.
> 
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS request did not succeed). Status code: (null).
> 
> Server initialization failed TypeError: NetworkError when attempting to fetch resource. proxy-store.ts:55
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 204.
> 
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS request did not succeed). Status code: (null).
> 
> Server initialization failed TypeError: NetworkError when attempting to fetch resource. proxy-store.ts:55
> Loading failed for the <script> with source “http://local.httptoolkit.tech:8080/vendors~react-monaco-editor.bundle.js”. local.httptoolkit.tech:8080:1:1
> Monaco load failed Loading chunk vendors~react-monaco-editor failed.
> (error: http://local.httptoolkit.tech:8080/vendors~react-monaco-editor.bundle.js) base-editor.tsx:53
> [WDS] Disconnected! client:172
> Previous server version was null index.tsx:131
> Reporting error: Error: Failed to initialize application
>     <anonymous> index.tsx:133
>     fulfilled index.tsx:33
>     promise callback*step index.tsx:35
>     __awaiter index.tsx:36
>     __awaiter index.tsx:32
>     <anonymous> index.tsx:130
>     promise callback* index.tsx:130
>     tsx app.js:28721
>     __webpack_require__ app.js:105
>     0 app.js:29657
>     __webpack_require__ app.js:105
>     <anonymous> app.js:275
>     <anonymous> app.js:278
>  
> Object {  }
> errors.ts:85
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 204.
> 
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS request did not succeed). Status code: (null).
> 
> Server initialization failed TypeError: NetworkError when attempting to fetch resource. proxy-store.ts:55
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 204.
> 
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS request did not succeed). Status code: (null).
> 
> Server initialization failed TypeError: NetworkError when attempting to fetch resource. proxy-store.ts:55
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 204.
> 
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS request did not succeed). Status code: (null).
> 
> Server initialization failed TypeError: NetworkError when attempting to fetch resource. proxy-store.ts:55
> Loading failed for the <script> with source “http://local.httptoolkit.tech:8080/vendors~react-monaco-editor.bundle.js”. local.httptoolkit.tech:8080:1:1
> Monaco load failed Loading chunk vendors~react-monaco-editor failed.
> (error: http://local.httptoolkit.tech:8080/vendors~react-monaco-editor.bundle.js) base-editor.tsx:53
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 204.
> 
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS request did not succeed). Status code: (null).
> 
> Server initialization failed TypeError: NetworkError when attempting to fetch resource. proxy-store.ts:55
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 204.
> 
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:45456/start. (Reason: CORS request did not succeed). Status code: (null).
> 
> Server initialization failed TypeError: NetworkError when attempting to fetch resource. proxy-store.ts:55
> Loading failed for the <script> with source “http://local.httptoolkit.tech:8080/vendors~react-monaco-editor.bundle.js”. local.httptoolkit.tech:8080:1:1
> Monaco load failed Loading chunk vendors~react-monaco-editor failed.
> (error: http://local.httptoolkit.tech:8080/vendors~react-monaco-editor.bundle.js)

The errors kept on going and basically the UI just stuck in the "This is taking longer than normal" message and never went through.
I've also tried to build the UI first and put the resulting files to my nginx server instead and still got the same errors.

root@s1:~/httptoolkit# npm run build

> prebuild
> rimraf dist


> build
> run-script-os


> build:default
> env-cmd -f ./automation/ts-node.env.js node --max_old_space_size=4096 node_modules/.bin/webpack --config ./automation/webpack.prod.ts

Sentry source map upload disabled - no token set
Hash: d273fc0ee11dad958a8c
Version: webpack 4.46.0
Time: 102629ms
Built at: 08/10/2023 17:12:55

LOG from InjectManifest
<i> The service worker at ui-update-worker.js will precache
<i>         32 URLs, totaling 21.7 MB.

I've tried using Firefox and Chrome browser with no avail. https://app.httptoolkit.tech/ worked just fine with those two browsers.
I'm using the latest server build from https://github.com/httptoolkit/httptoolkit-server/releases.

Any idea on what I'm doing wrong here ? I would greatly appreciate any assistance, thank you.

[Suggestion] Features

Hello,

I've been using HttpToolkit for a bit. I was using fiddler and mitmproxy in the past.

Here are a few feature suggestions

  1. Column customization in list view (like response payload size)
  2. Delete selected request/responses according to filters (or with CTRL+click) instead of all of them.
  3. Don't capture some request/responses according to filters.
  4. Import/export filters (to better use 3.)
  5. Transform response contents (like in JsonEditorOnline or with jq / jsonpath)
  6. Replay request (with modification) (like in Fiddler)
  7. Ask for confirmation to load the content on big responses payload (as loading the json viewer on big files hangs for a bit for instance)

@pimterry

Couldn't run due to ts error?

C:\Users\quantum\Desktop\projects\http-toolkit\httptoolkit-ui\node_modules\ts-node\src\index.ts:434
    return new TSError(diagnosticText, diagnosticCodes)
           ^
TSError: ⨯ Unable to compile TypeScript:
automation/webpack.dev.ts:6:22 - error TS2345: Argument of type 'import("C:/Users/quantum/Desktop/projects/http-toolkit/httptoolkit-ui/node_modules/@types/webpack/index").Configuration' is not assignable to parameter of type 'import("C:/Users/quantum/Desktop/projects/http-toolkit/httptoolkit-ui/node_modules/@types/webpack-merge/node_modules/webpack/types").Configuration'.
  Types of property 'cache' are incompatible.
    Type 'boolean | object | undefined' is not assignable to type 'boolean | MemoryCacheOptions | FileCacheOptions | undefined'.
      Type 'object' is not assignable to type 'boolean | MemoryCacheOptions | FileCacheOptions | undefined'.
        Property 'type' is missing in type '{}' but required in type 'FileCacheOptions'.

6 export default merge(common, {
                       ~~~~~~

  node_modules/@types/webpack-merge/node_modules/webpack/types.d.ts:3889:2
    3889  type: "filesystem";
          ~~~~
    'type' is declared here.

    at createTSError (C:\Users\quantum\Desktop\projects\http-toolkit\httptoolkit-ui\node_modules\ts-node\src\index.ts:434:12)
    at reportTSError (C:\Users\quantum\Desktop\projects\http-toolkit\httptoolkit-ui\node_modules\ts-node\src\index.ts:438:19)
    at getOutput (C:\Users\quantum\Desktop\projects\http-toolkit\httptoolkit-ui\node_modules\ts-node\src\index.ts:578:36)
    at Object.compile (C:\Users\quantum\Desktop\projects\http-toolkit\httptoolkit-ui\node_modules\ts-node\src\index.ts:775:32)
    at Module.m._compile (C:\Users\quantum\Desktop\projects\http-toolkit\httptoolkit-ui\node_modules\ts-node\src\index.ts:858:43)
    at Module._extensions..js (node:internal/modules/cjs/loader:1137:10)
    at Object.require.extensions.<computed> [as .ts] (C:\Users\quantum\Desktop\projects\http-toolkit\httptoolkit-ui\node_modules\ts-node\src\index.ts:861:12)
    at Module.load (node:internal/modules/cjs/loader:988:32)
    at Function.Module._load (node:internal/modules/cjs/loader:828:14)
    at Module.require (node:internal/modules/cjs/loader:1012:19)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
➜ httptoolkit-ui git:(master)✗

I am using node v16 i hope that's not causing this issue? npm doesn't seems to work on windows tbh.

darwin-arm64 error

it was fine for commit 07c8da06caf467def52b2da6086a2a72b74b7a20 (when I first cloned this)
But after pull latest update i get this error:
there is a missing build for darwin-arm64

[start:web   ] 
[start:web   ] > [email protected] start:web
[start:web   ] > env-cmd -f ./automation/ts-node.env webpack-dev-server --config ./automation/webpack.dev.ts
[start:web   ] 
[start:server] 
[start:server] > [email protected] start:server
[start:server] > npm-run-all server:setup server:start
[start:server] 
[start:server] 
[start:server] > [email protected] server:setup
[start:server] > ts-node -P ./automation/tsconfig.json ./automation/setup-server.ts
[start:server] 
[start:web   ] ℹ 「wds」: Project is running at http://local.httptoolkit.tech:8080/
[start:web   ] ℹ 「wds」: webpack output is served from /
[start:web   ] ℹ 「wds」: Content not from webpack is served from /Users/orangganteng/Workspaces/httptoolkit-ui/dist
[start:web   ] ℹ 「wds」: 404s will fallback to /index.html
[start:server] Downloading latest httptoolkit-server...
[start:server] Error: No server download available matching /httptoolkit-server-v[\d\.]+-darwin-arm64\.tar\.gz/
[start:server]     at /Users/orangganteng/Workspaces/httptoolkit-ui/automation/setup-server.ts:79:15
[start:server]     at Generator.next (<anonymous>)
[start:server]     at /Users/orangganteng/Workspaces/httptoolkit-ui/automation/setup-server.ts:31:71
[start:server]     at new Promise (<anonymous>)
[start:server]     at __awaiter (/Users/orangganteng/Workspaces/httptoolkit-ui/automation/setup-server.ts:27:12)
[start:server]     at downloadServer (/Users/orangganteng/Workspaces/httptoolkit-ui/automation/setup-server.ts:90:12)
[start:server]     at /Users/orangganteng/Workspaces/httptoolkit-ui/automation/setup-server.ts:37:15
[start:server]     at Generator.next (<anonymous>)
[start:server]     at fulfilled (/Users/orangganteng/Workspaces/httptoolkit-ui/automation/setup-server.ts:28:58)
[start:server]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[start:server] ERROR: "server:setup" exited with 1.
[start:web   ] 
[start:web   ] /Users/orangganteng/Workspaces/httptoolkit-ui/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:4
[start:web   ]     return new (P || (P = Promise))(function (resolve, reject) {
[start:web   ]            ^
[start:web   ] RpcIpcMessagePortClosedError: Process 7295 exited [SIGTERM].
[start:web   ]     at /Users/orangganteng/Workspaces/httptoolkit-ui/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:19:23
[start:web   ]     at Generator.next (<anonymous>)
[start:web   ]     at /Users/orangganteng/Workspaces/httptoolkit-ui/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:8:71
[start:web   ]     at new Promise (<anonymous>)
[start:web   ]     at __awaiter (/Users/orangganteng/Workspaces/httptoolkit-ui/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:4:12)
[start:web   ]     at ChildProcess.handleExit (/Users/orangganteng/Workspaces/httptoolkit-ui/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:18:42)
[start:web   ]     at ChildProcess.emit (node:events:513:28)
[start:web   ]     at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)

linux public network IP:45456/start CROS error

Hello, I deployed the httptoolkit-server and httptoolkit-ui services in the main branch separately in the Linux server. I ran npm start in the httptoolkit-server directory and npm run start:web in the httptoolkit-ui directory. After the services were started successfully, I tried Use the public IP in the browser to access the UI interface. When accessing http://xxx:45456/start, a cross-domain problem is reported. Does this tool support deployment using public IP addresses? Or do I need to modify any configuration so that I can normally use the public IP to access the UI and use related functions?
image

image

Allow getting SSL-Certificate

Hi!

I just tried out httptoolkit on mac. Works good on anything http-like, however I found no way to get a SSL Certificate I could import into my keychain so its able to intercept SSL-Traffic as well.

Steps to reproduce

Can't build

npm i
npm WARN deprecated @types/[email protected]: This is a stub types definition for react-ga (https://github.com/react-ga/react-ga). react-ga provides its own type definitions, so you don't need @types/react-ga installed!
npm WARN deprecated @types/[email protected]: This is a stub types definition. classnames provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated [email protected]: Removed event-stream from gulp-header
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/pinpoint'
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Fixed a prototype pollution security issue in 4.1.0, please upgrade to ^4.1.1 or ^5.0.1.
npm WARN deprecated [email protected]: "Please update to latest v2.3 or v2.2"
npm WARN deprecated [email protected]: "Please update to latest v2.3 or v2.2"
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/formula'
npm WARN deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: 3.x is no longer supported
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address'
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: This package has been renamed to @vscode/emmet-helper, please update to the new name
npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'
npm WARN deprecated [email protected]: Please upgrade to v7.0.2+ of superagent.  We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing.  See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>. Thanks to @shadowgate15, @spence-s, and @niftylettuce. Superagent is sponsored by Forward Email at <https://forwardemail.net>.
npm WARN deprecated [email protected]: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated [email protected]: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 1
npm ERR! path /Users/quantum/Desktop/projects/learn/httptoolkit-ui/node_modules/@sentry/cli
npm ERR! command failed
npm ERR! command sh /var/folders/q7/qy7ng_2x7zsflljr40gfmjmm0000gn/T/install-682cc78c.sh
npm ERR! Error: Unable to download sentry-cli binary from https://downloads.sentry-cdn.com/sentry-cli/1.61.0/sentry-cli-Darwin-x86_64.
npm ERR! Error code: ECONNREFUSED

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/quantum/.npm/_logs/2022-09-11T19_21_56_248Z-debug-0.log

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.