Absolutely! You can absolutely set up Eclipse (with Nodeclipse) to use a Node.js environment running inside a Docker container—no local Node.js installation needed at all. Let’s walk through exactly how to configure this, and fix that TypeScript import error you’re stuck on.

First, we need to get a Node.js Docker container running and link it to your Eclipse setup.

• Step 1: Spin up a persistent Node.js container
  Use the official Node.js Docker image to create a long-running container that mounts your project directory. Run this command in your terminal (replace /path/to/your/project with the actual path to your Eclipse project folder):

  docker run -d --name dev-node -v /path/to/your/project:/app -w /app node:20-alpine tail -f /dev/null
  

  This keeps the container running in the background, maps your local project folder to /app inside the container, and sets /app as the working directory.

• Step 2: Hook Eclipse/Nodeclipse to the container's Node.js
  Eclipse needs a way to call Node.js inside the container. We’ll create a small wrapper script to handle the Docker exec command:

  • For Linux/macOS: Create a file named docker-node.sh with this content:

    #!/bin/bash
    docker exec dev-node node "$@"
    

    Make it executable with chmod +x docker-node.sh.
  • For Windows: Create a file named docker-node.bat with this content:

    @echo off
    docker exec dev-node node %*
    

  Now, open Eclipse and go to Window > Preferences > Nodeclipse > Node.js. Select "Custom" under "Node.js installation", then browse to the wrapper script you just created. Test it by opening Eclipse’s terminal and running node --version—it should return the Node.js version from your Docker container.

The import errors happen because Eclipse’s TypeScript language service can’t find your project’s dependencies (and their type definitions) since you don’t have Node.js/npm locally. Here’s how to fix this:

• Step 1: Install dependencies via Docker
  Run this command to install your project’s dependencies inside the container—they’ll be saved to your local project’s node_modules folder thanks to the volume mount:

  docker exec dev-node npm install
  

• Step 2: Tweak your tsconfig.json
  Make sure your project’s tsconfig.json includes settings that help Eclipse resolve imports and types:

  {
    "compilerOptions": {
      "module": "commonjs",
      "target": "ES6",
      "baseUrl": ".",
      "paths": { "*": ["node_modules/*"] },
      "typeRoots": ["node_modules/@types"]
    },
    "include": ["src/**/*"]
  }
  

• Step 3: Refresh Eclipse's project view
  Right-click your project in Eclipse’s Project Explorer and select Refresh (or press F5). This lets Eclipse detect the newly created node_modules folder, and the import errors should disappear immediately.

You can even configure Eclipse to run and debug your app directly using the Docker container:

1. Go to Run > Run Configurations and create a new "Node.js Application" configuration.
2. In the "Main" tab, select your project’s entry file (e.g., src/index.ts).
3. Under "Node.js installation", select the wrapper script you set up earlier.
4. Click "Run"—Eclipse will execute your app via the Docker container, and you can use all its debugging tools like breakpoints as usual.

• Make sure your Docker daemon is running before starting Eclipse or any container commands.
• If you update your package.json, re-run docker exec dev-node npm install and refresh the project in Eclipse.
• For npm scripts (like build or test), run them via the container with docker exec dev-node npm run <script-name> in Eclipse’s terminal.

内容的提问来源于stack exchange，提问作者SNO