feat(pack): Support auto public path in UtooPack

[xusd320]

Summary

• add UtooPack support for output.publicPath: "auto"
• map the new config value to a Turbopack runtime marker and avoid treating it as a literal dev/HTML prefix
• add a public_path/auto snapshot fixture and refresh affected runtime snapshots
• update the next.js submodule pointer to include the Turbopack runtime support from feat(turbopack): Support auto public path in Turbopack runtime next.js#149

Why

The existing default publicPath behavior resolves to /, while publicPath: "runtime" reads globalThis.publicPath. This adds a webpack-compatible "auto" mode for deployments where chunks and assets should resolve relative to the current runtime script URL.

Validation

• cargo run -p pack-schema
• UPDATE=1 cargo test -p pack-tests public_path -- --nocapture
• cargo test -p pack-tests public_path -- --nocapture
• npm run build --workspace @utoo/pack-shared
• npm run build:js --workspace @utoo/pack
• cargo fmt
• cargo clippy --all-targets -- -D warnings --no-deps
• git diff --check
• git -C next.js diff --check

[gemini-code-assist]

Code Review

This pull request implements an 'auto' public path feature, which enables the runtime to automatically determine the base URL for assets based on the source of the executing script. The changes span the core configuration logic in Rust, the TypeScript build plugins, and the ECMAScript runtime. Feedback from the review points out that the string matching for the 'runtime' and 'auto' configuration keywords should be improved to handle trailing slashes, ensuring that user-provided values like 'auto/' are correctly identified as special modes rather than literal paths.

[gemini-code-assist]

The current implementation of computed_public_path handles the special values "runtime" and "auto" before enforcing a trailing slash. This is correct as these are internal markers. However, if a user provides "auto/" or "runtime/" in their configuration, they will fall through to the default case and be returned as literal paths with a trailing slash (e.g., "auto/"), which is likely not the intended behavior. Consider normalizing the input by trimming trailing slashes before matching against these keywords to be more resilient to user input.

[gemini-code-assist]

The normalizeHtmlPublicPath function correctly returns an empty string for "runtime" and "auto" modes, which is appropriate for static HTML injection where assets are typically co-located. However, similar to the Rust implementation, it only matches exact strings. If a user provides "auto/" in their configuration, it will return "auto/", leading to broken URLs like auto//main.js during asset injection. Consider using a more robust check or normalizing the input string.

References

1. Ensure that configuration keywords are handled consistently and resiliently across different parts of the codebase. ^(link)