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
I'm trying to migrate away from @babel to swc, and stuck with this one issue.
We're using .scss files for development and processing those into css during builds.
In case of @babel - it is possible to setup transformation, that will change sass/less into css. And there is ability to work with import extensions in general.
Only thing that I've found for SWC was this - swc-project/plugins#47 and, unfortunately, this behavior was fixed and not available any more.
Can you add ability to change imports during builds? You know, this is pretty weird idea to go away from babel, so later I would have to use swc + babel to finalize compilation.
Or there is already something to implement similar logic (except use babel to process compiled code)?
Babel plugin or link to the feature description
transform-rename-import
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the feature
I'm trying to migrate away from @babel to swc, and stuck with this one issue.
We're using .scss files for development and processing those into css during builds.
In case of @babel - it is possible to setup transformation, that will change sass/less into css. And there is ability to work with import extensions in general.
Only thing that I've found for SWC was this - swc-project/plugins#47 and, unfortunately, this behavior was fixed and not available any more.
Can you add ability to change imports during builds? You know, this is pretty weird idea to go away from babel, so later I would have to use swc + babel to finalize compilation.
Or there is already something to implement similar logic (except use babel to process compiled code)?
Babel plugin or link to the feature description
transform-rename-import
Additional context
No response
The text was updated successfully, but these errors were encountered: