Watch

History

Repository files (latest commit first)
Filename	Latest commit message	Latest commit date
cliffhall 1b754f52ca This fixes #214 where when the inspector is started, it can report that the inspector is up, when in fact it isn't because the address is already in use. It catches this condition, as well as the condition where the proxy server port is in use, reports it, and exits. * In bin/cli.js - in the delay function, have the setTimeout return a true value. - try the server's spawnPromise call and within the try block, use Promise.race to get the return value of the first promise to resolve. If the server is up, it will not resolve and the 2 second delay will resolve with true, telling us the server is ok. Any error will have been reported by the server startup process, so we will not pile on with more output in the catch block. - If the server started ok, then we will await the spawnPromise call for starting the client. If the client fails to start it will report and exit, otherwise we are done and both servers are running and have reported as much. If an error is caught and it isn't SIGINT or if process.env.DEBUG is true then the error will be thrown before exiting. * In client/bin/cli.js - add a "listening" handler to the server, logging that the MCP inspector is up at the given port - Add an "error" handler to the server that reports that the client port is in use if the error message includes "EADDRINUSE", otherwise throw the error so the entire contents can be seen. * In server/src/index.ts - add a "listening" handler to the server, logging that the Proxy server is up at the given port - Add an "error" handler to the server that reports that the server port is in use if the error message includes "EADDRINUSE", otherwise throw the error so the entire contents can be seen. * In package.json - in preview script - add --port 5173 to start the client on the proper port. This was useful in getting an instance of the client running before trying the start script. otherwise it starts on 4173		2025-03-28 11:59:21 -04:00
..
bin	This fixes #214 where when the inspector is started, it can report that the inspector is up, when in fact it isn't because the address is already in use. It catches this condition, as well as the condition where the proxy server port is in use, reports it, and exits.	2025-03-28 11:59:21 -04:00
public	switch favicon	2024-11-19 14:13:19 -08:00
src	Merge branch 'main' into add-ui-tests	2025-03-24 12:01:41 -07:00
.gitignore	init client	2024-10-07 16:28:05 -07:00
components.json	run prettier	2024-11-04 21:29:59 +00:00
eslint.config.js	init client	2024-10-07 16:28:05 -07:00
index.html	switch favicon	2024-11-19 14:13:19 -08:00
jest.config.cjs	Fix formatting	2025-03-24 09:07:53 -07:00
package.json	This fixes #214 where when the inspector is started, it can report that the inspector is up, when in fact it isn't because the address is already in use. It catches this condition, as well as the condition where the proxy server port is in use, reports it, and exits.	2025-03-28 11:59:21 -04:00
postcss.config.js	run prettier	2024-11-04 21:29:59 +00:00
README.md	init client	2024-10-07 16:28:05 -07:00
tailwind.config.js	Make tailwind config work on Windows	2024-11-26 16:51:50 +01:00
tsconfig.app.json	Add jest-dom types	2025-03-23 13:22:31 -07:00
tsconfig.jest.json	Handle edge case and add tests for functions	2025-02-27 06:40:01 -07:00
tsconfig.json	init client	2024-10-07 16:28:05 -07:00
tsconfig.node.json	init client	2024-10-07 16:28:05 -07:00
vite.config.ts	Update Vite configuration to enable host access and fix proxy server URL to use the current hostname.	2025-03-20 22:04:59 +08:00

README.md

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

@vitejs/plugin-react uses Babel for Fast Refresh
@vitejs/plugin-react-swc uses SWC for Fast Refresh

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

Configure the top-level parserOptions property like this:

export default tseslint.config({
  languageOptions: {
    // other options...
    parserOptions: {
      project: ["./tsconfig.node.json", "./tsconfig.app.json"],
      tsconfigRootDir: import.meta.dirname,
    },
  },
});

Replace tseslint.configs.recommended to tseslint.configs.recommendedTypeChecked or tseslint.configs.strictTypeChecked
Optionally add ...tseslint.configs.stylisticTypeChecked
Install eslint-plugin-react and update the config:

// eslint.config.js
import react from "eslint-plugin-react";

export default tseslint.config({
  // Set the react version
  settings: { react: { version: "18.3" } },
  plugins: {
    // Add the react plugin
    react,
  },
  rules: {
    // other rules...
    // Enable its recommended rules
    ...react.configs.recommended.rules,
    ...react.configs["jsx-runtime"].rules,
  },
});