chore(deps): bump vite-plus to v0.2.2#11
Draft
fengmk2 wants to merge 36 commits into
Draft
Conversation
…peScript - Migrate all extension initialization files from .js to .ts across cache, cron, crypto, ffi, fs, io, kv, node, runtime, web, webidl, websocket, and webstorage modules - Add TypeScript type definitions file (deno-extensions.d.ts) for runtime extensions - Reorganize rari module structure: consolidate core functionality into rari/core/rari.ts and split RSC logic into separate modules (rsc_modules.ts, server_functions.ts) - Extract shared utilities into new init_utilities extension with utilities.ts for common helper functions - Update module imports to use init_utilities instead of direct rari module references - Remove obsolete module directories: rsc_modules, server_functions, react modules now integrated into main rari extension - Migrate module loader utilities and add react_vendor.rs for vendor-specific React module handling - Update runtime factory, executor, and interface to work with TypeScript extensions - Simplify renderer.rs calls from add_module_to_loader_only() to add_module_to_loader() - Update Vite and ESLint configurations to support TypeScript extension files - Consolidate runtime initialization and improve module resolution pattern consistency
refactor(runtime): migrate remaining extensions from JavaScript to TypeScript
…tension - Flatten actions and components modules by moving mod.rs to parent directory - Flatten utils module and update dependencies export path - Simplify JsonValue type alias to use Value directly across actions module - Remove promise_manager extension and related initialization code - Remove promise_manager_check.js validation script from extension checks - Update extension_checks.js to remove PromiseManager requirement validation - Update module imports and public exports to reflect flattened structure - Consolidates module hierarchy for improved maintainability and reduces unnecessary nesting
refactor(rsc): flatten module structure and remove promise manager extension
…ce crate - Extract RSC core types and logic into new `rari-rsc` workspace crate - Move RSC components, flight protocol, types, and utilities from `crates/rari` to `crates/rari-rsc` - Reorganize module structure: components, core types, flight serialization/deserialization, and parser utilities - Add new dependencies to workspace: base64, parking_lot, smallvec, tracing, uuid - Update internal imports across rsc rendering, streaming, and server modules to use new crate path - Improve separation of concerns by isolating RSC-specific logic from main runtime - Update module loader, cache warmup, and request handling to work with relocated types - Consolidate RSC flight protocol implementation with improved escape and serialization utilities
- Move rendering module from rsc submodule to top-level of rari crate - Restructure core rendering logic with dedicated files for constants, loader, renderer, types, and utilities - Reorganize HTML rendering with improved module boundaries - Extract layout rendering into separate module with route composition and error messaging - Refactor streaming renderer with boundary management and promise resolution - Consolidate component isolation, server functions, and state management into core - Simplify RSC flight parser conditional logic for reference type checking - Remove redundant RSC module wrapper and update public API exports - Add clippy lint expectations for complex parsing logic in rari-rsc crate - Update runtime operations and server handlers to reflect new module structure
refactor(rsc): extract React Server Components into dedicated workspace crate
…crates - Organize module imports at the top of files using std prelude patterns - Consolidate repeated imports from deno_core, std modules, and external crates - Replace fully qualified paths with imported type aliases for brevity and readability - Move file-scoped imports to module level to follow Rust conventions - Simplify type references in trait implementations (Display, Formatter, Result, etc.) - Reorganize rendering module structure and relocate base rendering components - Update import paths for relocated rendering utilities and loaders - Improve code organization by grouping related imports and reducing redundancy
refactor(imports): consolidate and optimize import statements across crates
Replace custom RSC streaming implementation with React's official react-server-dom-webpack renderer and integrate Fizz-based server-side rendering for improved hydration and standards compliance. Key changes: - Replace custom React Flight client (~1,300 LOC) with react-server-dom-webpack - Implement Fizz (renderToReadableStream) for SSR with proper hydration markers - Migrate core rendering modules from JavaScript to TypeScript - Add Fizz marker detection for intelligent hydration vs render decisions - Remove custom streaming renderer, promise resolver, and boundary manager - Consolidate RSC rendering into simplified rsc_renderer.ts and fizz_render.ts - Add tools/bundle-react-esm for React ESM module bundling - Update client runtime to use hydrateRoot when Fizz markers detected - Remove 43 obsolete files including custom component isolation and promise tracking - Refactor server handlers and loaders for new rendering pipeline This migration reduces complexity by ~7,000 LOC while improving compatibility with React's official RSC implementation and enabling better SSR/hydration.
- Replace `std::` prefixed imports with aliased imports at module scope - Add `absolute_paths` lint warning to workspace Cargo.toml for consistency - Update error trait references from `std::error::Error` to imported `error::Error` - Convert `std::io::Error` imports to `io` alias in error handling module - Simplify `std::sync::OnceLock` to imported `OnceLock` in component registry - Replace `std::borrow::Cow` with imported `Cow` type alias - Update `std::string::ToString` import in RSC types module - Consolidate imports across runtime, server, and rendering modules - Improves code readability and reduces verbosity throughout codebase - Aligns with project's import organization standards
… processes - Added detailed error logging for composition and streaming navigation failures. - Improved error handling in the script execution for streaming, ensuring proper error messages are sent to the chunk sender. - Updated hydration error handling in the client to display user-friendly messages when loading fails. - Refactored manifest parsing to streamline error management and improve clarity.
…tion process - Added `invalidate_static_fast_cache_for_path` function to remove cache entries based on path. - Integrated cache invalidation into the `revalidate_by_path` handler for improved cache management. - Updated tests to verify cache invalidation behavior and ensure correctness of the caching mechanism.
…trol - Added `load_from_env_for_mode` and `load_from_env_with_base_for_mode` methods to streamline environment configuration loading based on the application mode. - Introduced cache control settings for server components based on the mode (production or development). - Updated tests to verify the correct application of cache control settings in production mode. - Removed obsolete React stubs to simplify the module loader and improve clarity.
- Moved metadata route types from `../types/metadata-route` to a new `./metadata-route` file for better organization. - Updated imports across the codebase to reflect the new file structure. - Refactored server configuration types to be sourced from `./server-config` instead of `../types/server-config` for consistency.
…code - Deleted the `renderWireToFizzStream` function from the JavaScript rendering layer. - Removed the corresponding TypeScript type definition for `renderWireToFizzStream`. - Cleaned up unused imports and code in the Rust rendering implementation.
refactor: migrate to official React Server Components with Fizz SSR
chore(dependencies): update various dependencies and improve project structure
refactor(runtime): replace hardcoded NODE_VERSION with deno_node constant
|
Warning Gemini encountered an error creating the review. You can try again by commenting |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump
vite-plusand related packages to the pkg.pr.new prerelease build for v0.2.2 (registry-bridge commit build) to smoke-test the prerelease.vite-plus+vite(alias to@voidzero-dev/vite-plus-core) andvitestpinned to the commit build across deps / overrides / catalogsminimumReleaseAgeenabled with thevite-plus/@voidzero-dev/*/ oxc / oxlint stack excluded.npmrc(or.yarnrc.yml) points the package manager at the registry bridge (prerelease scaffolding)Test plan