According to the documentation, the 'composite' option should be set to
'true' for referenced projects.

- The main.ts reference is fundamentally different from the favicon.ico
  reference, Vite resolves references like this similarly to how JavaScript
  imports are resolved.
- '@/main.ts' in index.html that uses 'resolve.alias' works properly for the
  production build but doesn't work for the development server.

Fixes TypeScript's "Cannot find type definition file for 'node'".

Fixes TypeScript's "Non-relative paths are not allowed when 'baseUrl' is not
set. Did you forget a leading './'?"

This makes it possible to perform check-only builds of a project that
uses 'references' in tsconfig.json. The '--noEmit' flag cannot be used
here because it is incompatible with '--build'. Check-only builds are
especially important for 'vue-tsc' as it doesn't support emitting files.

- 'vue-tsc' uses '--build' because we are using 'references' in
  tsconfig.json.
- 'vue-tsc' doesn't use '--noEmit' because it is incompatible with
  '--build'. Instead we set 'noEmit' to 'true' in the referenced
  tsconfig.json files.
- 'vue-tsc' uses '--force' to make check-only builds more reliable (see
  vuejs/create-vue#274).

…ncies

Because unfortunately, they don't work as expected.

- '...tseslint.configs.recommendedTypeChecked' enables enhanced linting
  with type information.
- 'languageOptions.parserOptions.EXPERIMENTAL_useProjectService: true'
  allows 'typescript-eslint' to compute type information for a
  TypeScript project that uses 'references' in the tsconfig.json file
  (see typescript-eslint/typescript-eslint#2094).