Need to treat json files and content as javascript

[rawasaditya]

Description

In our project we have alias imports we have written a plugin called aliasResolPlugin which will return absolute path in resolveId
Eg:
index.js
import js/xyz

after resolveId hook
index.js
import <absolute_path>/xyz.js

Now
I have written another plugin JsonUpdatePlugin which will add javascript code in *.json files, I have disabled vite:json plugin so that parsing will not throw an error

Eg:
index.json
import js/xyz

Since vite is not invoking resolveId hook for imports in json file of aliasResolPlugin I am not able replace these aliases with absolute Path

Suggested solution

There has to be a way to treat txt file or json file as javascript so that hook can get triggered

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[nozomuikuta]

Would you provide a minimal reproduction or a link to the repository so that other people can understand your issue better.
Knowing what to achieve (why you want to add JS code to JSON code), we can discuss how to achieve (currently only how is described).

[bluwy]

I assume this code is blocking from what you want to achieve:

vite/packages/vite/src/node/plugins/importAnalysis.ts

Lines 80 to 82 in da0caf5

	const skipRE = /\.(?:map|json)(?:$|\?)/
	export const canSkipImportAnalysis = (id: string): boolean =>
	skipRE.test(id) || isDirectCSSRequest(id)

Since JSON processing is builtin and your project is overriding its behaviour, I'd suggest having your plugin worked around it for now. In resolveId() you can resolve the .json file to e.g. .json.js, that way Vite doesn't see it as a JSON file and will process it.

I don't think Vite should open up or process JSON files as it adds overhead for everyone even if they don't change the JSON handling.