The behavior of the webpack loader and vite-plugin is inconsistent.

[ninesunsabiu]

In vite-plugin

js-lingui/packages/vite-plugin/src/index.ts

Lines 47 to 57 in 535d8dc

	async transform(src, id) {
	if (fileRegex.test(id)) {
	id = id.split("?")[0]
	const catalogRelativePath = path.relative(config.rootDir, id)
	const fileCatalog = getCatalogForFile(
	catalogRelativePath,
	await getCatalogs(config)
	)

the config is const config = getConfig(linguiConfig) in line: 20

js-lingui/packages/vite-plugin/src/index.ts

Line 20 in 535d8dc

const config = getConfig(linguiConfig)

---

but webpack loader

js-lingui/packages/loader/src/webpackLoader.ts

Lines 15 to 25 in 535d8dc

	const loader: LoaderDefinitionFunction<LinguiLoaderOptions> = async function (
	source
	) {
	const options = this.getOptions() || {}
	const config = getConfig({
	configPath: options.config,
	cwd: path.dirname(this.resourcePath),
	})
	const catalogRelativePath = path.relative(config.rootDir, this.resourcePath)

the config depends on this.resourcePath.

What behavior is expected
Actually, I used the behavior of webpack and discovered this issue when migrating to vite.

[ninesunsabiu]

I applied a patch to vite-plugin/src/index.ts so that I can have the same behavior as in webpack.

       async transform(src, id) {
         if (fileRegex.test(id)) {
           id = id.split("?")[0];
+          const config = getConfig({
+            configPath: linguiConfig.configPath,
+            cwd: path.dirname(id)
+          });
           const catalogRelativePath = path.relative(config.rootDir, id);
           const fileCatalog = getCatalogForFile(
             catalogRelativePath,