Skip to content

Commit 72e5455

Browse files
authoredJan 27, 2025··
fix(es): Restore JSON config & Adjust feature renaming (#9967)
**Description:** I made a mistake while applying deprecations
1 parent afda34f commit 72e5455

File tree

9 files changed

+11
-81
lines changed

9 files changed

+11
-81
lines changed
 

‎.changeset/sweet-ladybugs-lick.md

+6
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
swc: patch
3+
swc_core: patch
4+
---
5+
6+
fix(es): Restore JSON config

‎crates/swc/src/config/mod.rs

+4
Original file line numberDiff line numberDiff line change
@@ -1464,6 +1464,10 @@ pub struct TransformConfig {
14641464
#[serde(default)]
14651465
pub regenerator: regenerator::Config,
14661466

1467+
#[serde(default)]
1468+
#[deprecated]
1469+
pub treat_const_enum_as_enum: BoolConfig<false>,
1470+
14671471
/// https://www.typescriptlang.org/tsconfig#useDefineForClassFields
14681472
#[serde(default)]
14691473
pub use_define_for_class_fields: BoolConfig<true>,

‎crates/swc/src/plugin.rs

+1-1
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ impl RustPlugins {
5858

5959
let filename = self.metadata_context.filename.clone();
6060

61-
if cfg!(feature = "manual-tokio-runtmie") {
61+
if cfg!(feature = "manual-tokio-runtime") {
6262
self.apply_inner(n)
6363
} else {
6464
let fut = async move { self.apply_inner(n) };

‎crates/swc/tests/fixture/ts-inline-enum/treatConstEnumAsEnum-2/input/.swcrc

-10
This file was deleted.

‎crates/swc/tests/fixture/ts-inline-enum/treatConstEnumAsEnum-2/input/index.ts

-18
This file was deleted.

‎crates/swc/tests/fixture/ts-inline-enum/treatConstEnumAsEnum-2/output/index.ts

-12
This file was deleted.

‎crates/swc/tests/fixture/ts-inline-enum/treatConstEnumAsEnum/input/.swcrc

-10
This file was deleted.

‎crates/swc/tests/fixture/ts-inline-enum/treatConstEnumAsEnum/input/index.ts

-18
This file was deleted.

‎crates/swc/tests/fixture/ts-inline-enum/treatConstEnumAsEnum/output/index.ts

-12
This file was deleted.

0 commit comments

Comments
 (0)
Please sign in to comment.