You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Select content mapper at import level thanks to the with keywordΒ #65404
Extensions filter are too limitative for content mappers. I think that we should be able to use with keyword when importing module to select the right content mapper.
π Motivating Example
For example, with this content mapper : https://github.com/nfroidure/json-schema-content-mapper I have to import .jsonchema files but what I would like to do is to import schemas by URLs and I cannot change their extension.
Activity
nfroidure commentedon Nov 9, 2026
Just noticed that turbopack whaere just using its own props ( https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopack#inline-loader-configuration-with-import-attributes ), so maybe better to add as
tsContentMapperone.