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 }}
This repository was archived by the owner on Jan 16, 2025. It is now read-only.
Hi!
I often find myself in the need to specify same CLI (note, not the SWC options, the CLI one like --out-dir) options with slight variations (for instance, in production I don't build source-maps).
It would be great if all the options could be specified in a file similar to .swcrc. Ideally the file should be a different one but use the same syntax. As a side idea, we could even use the same .swcrc and open a new section there (like cli).
Is this possible and/or in the roadmap? Would you accept a PR for it?
The text was updated successfully, but these errors were encountered:
This PR add a new option that can point to JSON file. This file can contain any option supported by CLI (either in `kebab-case` or `camelCase` format) and will applied accordingly.
Other options explicitly provided via command line override the one in the JSON file (so that the file can act as a "template").
Fixesswc-project/cli#284.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi!
I often find myself in the need to specify same CLI (note, not the SWC options, the CLI one like
--out-dir
) options with slight variations (for instance, in production I don't build source-maps).It would be great if all the options could be specified in a file similar to
.swcrc
. Ideally the file should be a different one but use the same syntax. As a side idea, we could even use the same.swcrc
and open a new section there (likecli
).Is this possible and/or in the roadmap? Would you accept a PR for it?
The text was updated successfully, but these errors were encountered: