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
Is your feature request related to a problem? Please describe.
I tried using Subpath imports but they don't work. It would be great if it were possible to use native way no configure paths.
Describe the solution you'd like
Subpath imports should work the same way as aliases from tsconfig.json work now.
Describe alternatives you've considered
I don't know any alternatives for Subpath imports
Is your feature request related to a problem? Please describe.
I tried using Subpath imports but they don't work. It would be great if it were possible to use native way no configure paths.
Describe the solution you'd like
Subpath imports should work the same way as aliases from
tsconfig.json
work now.Describe alternatives you've considered
I don't know any alternatives for Subpath imports
Additional context
Article: https://betterprogramming.pub/the-native-way-to-configure-path-aliases-in-frontend-projects-5db70f19a6e0
Docs: https://nodejs.org/api/packages.html#subpath-imports
Now the plugin works in two cases:
relative path
import styles from "../styles/Home.module.css";
alias from
tsconfig.json
import styles from "@/styles/Home.module.css";
But if you use subpath imports you get an error:
import styles from "#styles/Home.module.css";
The text was updated successfully, but these errors were encountered: