Skip to content

Don't load vite.config.ts using import, rely on vite.resolveConfig only #278

@segevfiner

Description

@segevfiner

Prerequisites

  • I have written a descriptive issue title
  • I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal

If you currently use a vite.config.ts file, it will fail to load in

const resolvedConfig = await resolveConfig(
unless you use a loader that can support loading ts files directly such as tsx, this is not normally a requirement when you otherwise already build your TypeScript and run the built JS with Node. It makes more sense to not require this and rely only on Vite's resolveConfig to load the configuration.

Motivation

Not needing to use tsx to run a project with vite.config.ts that is otherwise already built.

Example

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions