swc/bindings
Donny/강동윤 0cd8aeeb5c
feat(bindings): Apply resolver to the output of parse apis (#6118)
**Description:**

This PR makes the `parse*()` API return AST with `resolver` applied to help plugin authors
2022-10-11 11:49:30 +00:00
..
binding_core_node feat(bindings): Apply resolver to the output of parse apis (#6118) 2022-10-11 11:49:30 +00:00
binding_core_wasm feat(bindings): Apply resolver to the output of parse apis (#6118) 2022-10-11 11:49:30 +00:00
node_macro_deps refactor(bindings): Use separate workspace for bindings (#5506) 2022-08-16 15:01:49 +09:00
swc_cli chore: Publish v1.3.6 (#6087) 2022-10-08 13:39:07 +09:00
Cargo.lock feat(bindings): Apply resolver to the output of parse apis (#6118) 2022-10-11 11:49:30 +00:00
Cargo.toml chore(ci): Merge CI scripts (#5999) 2022-09-30 16:57:15 +09:00
README.md refactor(bindings): Use separate workspace for bindings (#5506) 2022-08-16 15:01:49 +09:00

SWC bindings

This folder contains actual bindings binary SWC will build for the supported platforms (@swc/core, swc_cli, @swc/wasm).

All the bindings binary uses publicly published swc_core SDK to build deterministic host binary for the specific changes, in result Cargo's workspace gets confused to select dependency versions if it belongs to the workspace contains unpublished packages. To avoid those problems, these bindings are not being built as part of the workspace.