fix: resolve Send bounds and formatting issues

- Use tracing::debug! events instead of spans in Send-required contexts
  (NAPI run function and vite config resolver)
- Fix cargo fmt formatting in tracing.rs
- Add process.uptime() to JS startup timing for absolute timeline

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: branchseer

crates/vite_shared/src/tracing.rs

@@ -5,8 +5,7 @@
 //! - `VITE_LOG_OUTPUT`: Output format — `"chrome-json"` for Chrome DevTools timeline,
 //!   `"readable"` for pretty-printed output, or default stdout.
 
-use std::any::Any;
-use std::sync::atomic::AtomicBool;
+use std::{any::Any, sync::atomic::AtomicBool};
 
 use tracing_chrome::ChromeLayerBuilder;
 use tracing_subscriber::{
@@ -44,19 +43,16 @@ pub fn init_tracing() -> Option<Box<dyn Any + Send>> {
             .with_targets([("tokenize", LevelFilter::OFF), ("parse", LevelFilter::OFF)])
     };
 
-    let output_mode = std::env::var(env_vars::VITE_LOG_OUTPUT)
-        .unwrap_or_else(|_| "stdout".to_string());
+    let output_mode =
+        std::env::var(env_vars::VITE_LOG_OUTPUT).unwrap_or_else(|_| "stdout".to_string());
 
     match output_mode.as_str() {
         "chrome-json" => {
             let (chrome_layer, guard) = ChromeLayerBuilder::new()
                 .trace_style(tracing_chrome::TraceStyle::Async)
                 .include_args(true)
                 .build();
-            tracing_subscriber::registry()
-                .with(targets)
-                .with(chrome_layer)
-                .init();
+            tracing_subscriber::registry().with(targets).with(chrome_layer).init();
             Some(Box::new(guard))
         }
         "readable" => {

packages/cli/binding/src/lib.rs

@@ -98,7 +98,7 @@ fn create_vite_config_resolver(
     Arc::new(move |package_path: String| {
         let tsf = tsf.clone();
         Box::pin(async move {
-            let _span = tracing::debug_span!("js_resolve_vite_config").entered();
+            tracing::debug!("js_resolve_vite_config: start");
             let promise: Promise<String> = tsf
                 .call_async(Ok(package_path))
                 .await
@@ -120,7 +120,7 @@ fn create_vite_config_resolver(
 /// and process JavaScript callbacks (via ThreadsafeFunction).
 #[napi]
 pub async fn run(options: CliOptions) -> Result<i32> {
-    let _span = tracing::debug_span!("napi_run").entered();
+    tracing::debug!("napi_run: start");
     // Use provided cwd or current directory
     let mut cwd = current_dir()?;
     if let Some(options_cwd) = options.cwd {

packages/cli/src/bin.ts

@@ -46,8 +46,10 @@ if (command === 'create') {
 } else {
   // All other commands — delegate to Rust core via NAPI binding
   if (process.env.VITE_LOG) {
+    const processUptime = (process.uptime() * 1000).toFixed(2);
+    const jsModuleLoad = (performance.now() - jsStartTime).toFixed(2);
     console.log(
-      `[vite-plus] JS startup: ${(performance.now() - jsStartTime).toFixed(2)}ms`,
+      `[vite-plus] process uptime: ${processUptime}ms, JS module load: ${jsModuleLoad}ms`,
     );
   }
   run({