* chore(deps): upgrade pnpm to 11.1.1
Bumps the corepack-managed pnpm version across the root and the four
Angular example workspaces. pnpm 11 refuses to run install scripts by
default; declare a minimal allowBuilds allowlist in pnpm-workspace.yaml
so only the two packages whose postinstalls the build actually needs
(esbuild, nx) are permitted. The other eight transitively-pulled
postinstalls (sharp, lmdb, workerd, etc.) all fall back to JS paths
or are unused during build, and are explicitly denied.
Also pin the preinstall guard to only-allow@1.2.2 so it no longer
resolves a floating tag from npm on every install.
* ci(security): pin actions to SHAs and harden CI/CD supply chain
Replaces every mutable workflow reference (@main, @v1, @v3, @v4,
@v6.0.2) with a 40-char commit SHA + version comment so Renovate can
keep them current. Composite actions in TanStack/config — previously
pinned to @main — are the highest-impact change: a force-push or
compromised commit there would have given an attacker the npm OIDC
publishing identity plus contents/issues/PR write tokens on the next
push to main.
Other changes in this commit:
- release.yml: set cancel-in-progress: false so a re-push cannot abort
changesets/action mid-publish and leave partial versions on npm.
Add environment: release so required reviewers can be configured in
repo settings for an explicit human gate before publish.
- triage-agent.yml: add a "SECURITY: Untrusted input" preamble to the
Warp agent prompt. The agent reads attacker-controlled issue text,
so it must treat that text strictly as data and refuse instructions
embedded inside it. Also corrected the bug-report template path
(bug-report.yml -> bug_report.yml) that the agent was failing to
load.
- check-skills.yml / validate-skills.yml: pin @tanstack/intent to a
specific version; npm install -g without a version was floating.
- pr.yml preview job: pin pkg-pr-new to a specific version; pnpx
without a version was floating.
- .github/renovate.json: drop :automergeMinor. Combined with floating
versions this could have landed a malicious patch without review.
- .github/CODEOWNERS (new): require owner review on workflows, package
manifests, lockfile, .npmrc, and renovate config. Adjust the owner
handle to a team once one exists.
- .github/workflows/dependency-review.yml (new): runs
actions/dependency-review-action on every PR with
fail-on-severity: high to block PRs that introduce known-vulnerable
transitive dependencies.
* ci(security): bump TanStack/config pin to latest main SHA
* fix(ci): correct preinstall skip logic for CI
The original `||`-chained preinstall printed "Skipping preinstall..." in
CI but then ran only-allow anyway because `process.exit(1)` triggers
the `||` operator. CI happened to pass when only-allow was unpinned
(npx resolved it differently), but pinning to @1.2.2 forced a fresh
registry resolve in which only-allow strictly checks
npm_config_user_agent — which, when invoked via npx-inside-pnpm, is
npm's, not pnpm's — and rejects.
The fix matches the script's stated intent: when CI=true, exit 0 so
the `||` does not trigger and only-allow is genuinely skipped. Local
installs continue to fall through and enforce pnpm via only-allow as
before.
* refactor(devtools): remove SeoTab component and related functionality
This commit deletes the SeoTab component from the devtools package, which included social media preview functionality and meta tag analysis. The removal streamlines the codebase by eliminating unused features.
* refactor(devtools): rename SocialPreviewSection to SocialPreviewsSection
This commit updates the naming of the SocialPreviewSection component to SocialPreviewsSection for consistency and clarity in the SEO tab of the devtools package. The change improves code readability and aligns with the pluralization of the component's purpose.
* refactor(devtools): rename social-preview file to social-previews and update import path
This commit renames the social-preview.tsx file to social-previews.tsx for consistency with the component naming convention. The import path in the SeoTab component is also updated accordingly, enhancing code clarity and maintainability.
* feat(devtools): add SEO tab navigation and enhance SocialPreviewsSection
This commit introduces a navigation bar in the SeoTab component, allowing users to switch between 'Social Previews' and 'SERP Preview' sections. It also updates the SocialPreviewsSection to conditionally render its title based on a new prop, improving flexibility in display options. New styles for the navigation elements are added to enhance the user interface.
* feat(devtools): enhance SERP and Social Previews with new styles and data handling
This commit introduces new styles for the SERP snippet and updates the SERP and Social Previews sections to dynamically display data from the current page's metadata. The SocialPreviewsSection and SerpPreviewSection components are refactored to improve clarity and functionality, removing unnecessary props and enhancing the user interface with better styling.
* refactor(devtools): update SERP snippet styles and structure
This commit refactors the SERP snippet styles by renaming the `serpSnippetUrlRow` to `serpSnippetTopRow` and introduces new styles for site name and URL. The structure of the SERP preview is enhanced to better organize the display of site information, improving the overall layout and visual consistency.
* feat(devtools): enhance SERP preview with truncation logic and overflow reporting
This commit adds functionality to the SERP preview section, implementing text truncation for the title and description based on specified width limits. It introduces new state management for overflow detection and displays warnings when the title or description exceeds the defined character limits. Additionally, new styles are added to support the hidden measurement elements for accurate text sizing.
* feat(devtools): add SERP overflow reporting and improve styles
This commit enhances the SERP preview section by introducing a new overflow reporting mechanism for the title and description. It adds a list of issues when the title or description exceeds specified limits, improving user feedback. Additionally, new styles are implemented for better visual presentation of error messages in the SERP preview.
* feat(devtools): add meta description and default favicon styles
This commit enhances the SEO capabilities of the basic example by adding a meta description tag for improved search engine visibility. Additionally, it introduces new styles for a default favicon, ensuring a consistent visual representation when no favicon is provided. This improves user feedback in the SERP preview section.
* feat(devtools): enhance SERP preview layout with new styles
This commit introduces new styles for the SERP preview section, including a dedicated block for the preview and a label for better organization. The layout improvements enhance the visual presentation of the desktop preview, ensuring a clearer display of the site name, URL, title, and description.
* feat(devtools): enhance SERP preview for mobile with new styles and overflow reporting
This commit introduces new styles for the mobile SERP preview, including a dedicated snippet layout and improved overflow reporting for the title and description. It adds functionality to handle mobile-specific text truncation and displays warnings for descriptions exceeding a three-line limit, enhancing user feedback and visual consistency across devices.
* feat(devtools): implement comprehensive SERP issue reporting and enhance component structure
This commit introduces a robust mechanism for reporting SERP issues, including checks for favicon, title, and description validity. It refactors the SERP preview component to utilize a more structured approach for handling overflow conditions and displaying relevant warnings. Additionally, it enhances the layout for both desktop and mobile previews, ensuring a consistent and informative user experience across devices.
* refactor(devtools): update SERP preview truncation logic and improve character limits
This commit refines the SERP preview component by replacing pixel-based truncation with character-based limits for titles and descriptions. It introduces constants for maximum character counts, enhancing the clarity of the truncation logic. Additionally, it simplifies the component structure by removing unnecessary measurement elements, improving overall readability and maintainability.
* refactor(devtools): streamline SERP preview component and improve character limit handling
This commit refines the SERP preview component by enhancing the character limit handling for titles and descriptions. It simplifies the component structure, removing redundant elements, and improves the overall readability and maintainability of the code. Additionally, it ensures consistent behavior across different display scenarios.
* refactor(devtools): reorder imports in social-previews component for consistency
---------
Co-authored-by: Alem Tuzlak <t.zlak97@gmail.com>
* fix: include skills/ and bin/intent.js in npm publish for all packages
The skills/ directories and intent bin shim were missing from the
individual package.json files. The intent scanner requires both
"bin": { "intent": ... } and a skills/ directory to detect packages.
Without these, npx @tanstack/intent install reports "No intent-enabled
packages found."
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* fix(devtools): prevent solid-js from leaking into server bundles
Move all solid-js runtime imports (render, Portal, lazy, ClientEventBus)
from core into a new mount-impl.tsx file loaded via dynamic import().
This ensures solid-js code is never in the static import graph and only
loads as a separate chunk when mount() is called on the client.
* feat(devtools-utils): add Solid.js support and enhance routing configurations
* ci: apply automated fixes
* fix(devtools-utils): resolve self-referencing import for clean CI builds
Add ambient module declaration (barrel-types.d.ts) so TypeScript can
resolve @tanstack/devtools-utils/solid on clean checkouts without dist/.
* ci: apply automated fixes
* fix(devtools-utils): fix lint errors in solid class files
* fix(devtools-utils): use variable import path to prevent esbuild SSR pre-bundling
esbuild follows dynamic imports with string literals during Vite's
dependency optimization, pulling solid-js into the SSR bundle. Using a
variable path prevents static analysis from following the import.
* fix(devtools-utils): add workerd export condition to ./solid for Cloudflare SSR
The ./solid export was missing a workerd condition, causing Vite's SSR
dep optimizer (esbuild) to resolve to the client entry instead of
server.js when running under Cloudflare workerd. The client entry's
compiled Solid JSX imports use/setStyleProperty from solid-js/web which
don't exist in the server entry, crashing the dev server.
Also reverts the variable import workaround in class.ts back to a
literal import, since the workerd condition now properly routes SSR
resolution to the server entry.
* Refactor code structure for improved readability and maintainability
* fix(devtools-utils): use relative dynamic import for class-mount-impl
Replace the cross-package bare specifier import('@tanstack/devtools-utils/solid')
with a relative import('./class-mount-impl'). Bare specifiers in dynamic imports
inside pre-bundled dependencies aren't resolved by bundlers like esbuild/webpack,
causing "Failed to resolve module specifier" errors in the browser.
The relative import works in all bundlers (Vite, Next.js, etc.) because the
class-mount-impl.js file is co-located in the same dist directory, built
together via a single vite config with vite-plugin-solid for JSX compilation.
* ci: apply automated fixes
* chore: fix issues
* chore: changeset
* fix: lock
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* feat: simplify EventClient types to accept unprefixed event maps
EventClient now accepts event maps with plain event names instead of
requiring the pluginId prefix in every key. The prefix is handled
purely at runtime. This removes the complex conditional types that
were stripping prefixes from emit/on/createEventPayload signatures.
* ci: apply automated fixes
* chore: add patch changeset for event client type simplification
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* fix: add Alt modifier to inspect hotkey default to avoid browser conflicts
The previous default (Shift + CtrlOrMeta) overlaps with browser shortcuts
for opening links in new tabs (Ctrl/Cmd + Shift + Click in Chrome, Edge,
Safari). Adding Alt/Option as a third modifier avoids all known OS, browser,
and common web app shortcut collisions.
* chore: add changeset for inspect hotkey default change
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>