2.0.1

What's Changed

• add resolve^1.22.8 and debug^4.3.4 as dependency by @n0099 in #22

New Contributors

• @n0099 made their first contribution in #22

2.0.0

What's Changed

• Feature/2.0.0 by @pzmosquito in #21

Full Changelog: 1.3.2...2.0.0

2.0.0-beta.3

• fix some absolute path handling issues

1.3.2

• normalize path before splitting for parsing (550461b)

2.0.0-beta.1

This release changed how the Vite config is loaded. In version 1.x, this plugin loads and parses the Vite config file. This could be easier to set up for default use cases, but it also introduced the issue where the plugin has to use the require() function. This works in most setups but may not work as expected in some ESM - CJS mixed setups. To avoid this issue, version 2.x moved the responsibility of loading the Vite config to the users. The plugin will now accept the Vite config object. This means that users will have the flexibility to choose how they want to load the Vite config file suitable for their setups.

// version 1.x

settings: {
    "import/resolver": "vite"
}
// OR
settings: {
    "import/resolver": {
        vite: {
            configPath: "./app/vite.config.js",
            namedExport: "viteConfigObj"
        }
    }
}

// version 2.x

settings: {
    "import/resolver": {
        vite: {
            viteConfig: require("./vite.config").viteConfigObj,
        }
    }
}

1.3.1

• fix a publicdir resove issue (6054461)

1.3.0

• support array type alias (#9)
• fix a bug where the alias parsing should replace full directory name. (6fb8ff1)

1.2.1

• fix error in a rare case when resolved publicDir path contains characters in the alias option (3a657d9)
• update tests to be more robust (3a657d9)

1.2.0

• add support for importing assets from publicDir (6eb417c)

1.1.0

• add CJS vite config support (you don't need to have the extra default anymore) (8122440)