Regression - The entry point cannot be marked as external

[leepowelldev]

Vite version: 2.0.0-beta.52
Node version: v15.3.0
Platform: OS X 11.1

This has only happened in the release since yesterday. Given the following config:

import { resolve } from 'path';
import { defineConfig } from 'vite';

export default defineConfig({
  server: {
    open: false,
  },
  clearScreen: false,
  build: {
    manifest: true,
    sourcemap: true,
    rollupOptions: {
      input: {
        home: resolve(__dirname, './src/home.ts'),
        about: resolve(__dirname, './src/about.ts'),
      },
    },
  },
  plugins: [],
});

When npm run dev is run, the following error occurs:

> error: The entry point "/path/to/wordpress/wp-content/themes/skeleton/src/home.ts" cannot be marked as external

 > error: The entry point "/path/to/wordpress/wp-content/themes/skeleton/src/about.ts" cannot be marked as external

error when starting dev server:
Error: Build failed with 1 error:
error: The entry point "/path/to/home.ts" cannot be marked as external
    at failureErrorWithLog (/path/to/wordpress/wp-content/themes/skeleton/node_modules/esbuild/lib/main.js:969:15)
    at buildResponseToResult (/path/to/wordpress/wp-content/themes/skeleton/node_modules/esbuild/lib/main.js:767:32)
    at /path/to/wordpress/wp-content/themes/skeleton/node_modules/esbuild/lib/main.js:819:20
    at handleIncomingPacket (/path/to/wordpress/wp-content/themes/skeleton/node_modules/esbuild/lib/main.js:566:9)
    at Socket.readFromStdout (/path/to/wordpress/wp-content/themes/skeleton/node_modules/esbuild/lib/main.js:482:7)
    at Socket.emit (node:events:376:20)
    at addChunk (node:internal/streams/readable:304:12)
    at readableAddChunk (node:internal/streams/readable:279:9)
    at Socket.Readable.push (node:internal/streams/readable:218:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:192:23)

npm run build works as expected.

[ElMassimo]

Reproduction 🐞

The issue can be replicated in this application, by running pnpm install and pnpm dev.

Notes ✏️

build works as expected, so it's only related to the scanning of dependencies for optimization.

#1772 contains a possible fix.

[ais-one]

I may have a problem with this library "@jamescoyle/vue-icon": "^0.1.0"

Will create a simple use case and see into this problem more