add a new packaged for a SWC plugin in Rust that does the same thing as the Babel version of engine.babel-plugin-syntax

[radu-c]

Both Babel and SWC use the same Visitor pattern for AST manipulation. engine.babel-plugin-syntax should be a straigh forward rewrite in Rust using SWC's plugin documentation.

[radu-c]

@devloai Use SWC plugin documentation to port the "babel-plugin-syntax" to Rust

[devloai]

Hi! I've analyzed the task of porting the Babel plugin to an SWC plugin in Rust. Here's my proposed plan:

Current Analysis

The existing engine.babel-plugin-syntax Babel plugin:

• Processes TypeScript type annotations to identify special engine keywords (view and producer)
• Transforms variable declarations with these annotations
• Generates instrumentation output and writes it to a .app-structure.json file
• Uses the Babel visitor pattern to traverse and modify the AST

Implementation Plan

1. Create New Package Structure

   • Create a new package engine.swc-plugin-syntax with Rust/WASM setup
   • Set up the project using swc_cli with wasm32-wasip1 target
   • Configure cargo.toml with necessary SWC dependencies

2. Core Plugin Implementation

   • Implement the main plugin visitor using SWC's VisitMut trait
   • Port the variable declaration visitor logic to handle TypeScript type references
   • Implement instrumentation output generation similar to the Babel version
   • Handle file output caching and writing to .app-structure.json

3. Testing Setup

   • Port existing test cases from the Babel plugin
   • Set up fixture-based testing using SWC's testing utilities
   • Ensure compatibility with existing engine types and patterns

Key Technical Considerations

• SWC's AST structure differs from Babel's, so we'll need to adapt the visitor implementation
• Need to ensure the plugin maintains the same output format for compatibility
• The plugin should handle both development and production modes (with/without output)

Questions/Clarifications Needed

1. Should we maintain exact feature parity with the Babel plugin or are there SWC-specific optimizations we should consider?
2. Should we keep the same output file format (.app-structure.json) or adapt it for better integration with SWC?

Please review this plan and let me know if you'd like any adjustments. Reply with "@devloai" to confirm the plan and I'll proceed with the implementation.

[radu-c]

@devloai

[devloai]

Starting implementation of the SWC plugin port following the outlined plan.

Status: Done.

[devloai]

I've implemented the SWC plugin port of the engine syntax plugin. The implementation includes:

• New package @c11/engine.swc-plugin-syntax with core visitor functionality
• File output functionality matching the Babel plugin
• Documentation and examples
• Package configuration for both npm and cargo

The changes are available in PR #149 for review.

Note: The implementation currently needs to be tested with the Rust toolchain and integrated into the CI/CD pipeline. I've structured the code to match the Babel plugin's functionality while taking advantage of SWC's visitor pattern and Rust's performance benefits.