solidjs/solid

Begin with package exports and build/test configuration before editing runtime behavior, because environment selection changes implementation semantics. Keep client/server parity, owner cleanup, hydration IDs, and store safety guards explicit in any proposed change. Tests and CI were inspected, not executed, and this brief is a bounded source inventory rather than exhaustive coverage or validation.

• Use the repository's pnpm/Turbo workflow: root scripts coordinate build, types, tests, and coverage, and CONTRIBUTING documents pnpm install/build/test for an executable development session.
  package.json#L12-22package.json#L69-72CONTRIBUTING.md#L89-99
• Before changing a public API, read its core export, conditional package map, and Rollup target; source tests alias implementations, while consumers load built artifacts selected by environment.
  packages/solid/src/index.ts#L1-33packages/solid/package.json#L45-80packages/solid/rollup.config.js#L41-83packages/solid/vite.config.mjs#L30-37
• Treat signal.ts as a shared runtime hotspot: Observer/Listener slots, Owner trees, tentative transition state, and cleanup are coupled across readSignal, writeSignal, completeUpdates, and cleanNode.
  packages/solid/src/reactive/signal.ts#L1302-1338packages/solid/src/reactive/signal.ts#L1341-1375packages/solid/src/reactive/signal.ts#L1582-1614packages/solid/src/reactive/signal.ts#L1700-1737
• For store changes, read store.ts, modifiers.ts, and server.ts together and preserve unsafe-key traversal/merge guards, deletion semantics, and permitted leaf keys.
  packages/solid/store/src/store.ts#L228-274packages/solid/store/src/store.ts#L294-343packages/solid/store/src/server.ts#L32-79packages/solid/store/test/store.spec.ts#L907-943
• For asynchronous component changes, inspect both lazy implementations, resource/Suspense integration, and rejected-import regressions; the server test verifies a subsequent request retries the rejected module.
  packages/solid/src/render/component.ts#L359-426packages/solid/src/server/rendering.ts#L556-607packages/solid/src/render/Suspense.ts#L123-207packages/solid/test/server/lazy.spec.ts#L64-93
• In a separately authorized executable task, use the relevant Vitest file first, then the package test script for both environments and test-types for signature changes; these commands are recommendations, not results from this inspection. (inferred)
  packages/solid/package.json#L225-227packages/solid/vitest.server.config.mjs#L5-17packages/solid/tsconfig.test.json#L1-12
• Do not interpret inspected coverage as server validation: the client V8 report excludes server source, and the type-test configuration also excludes test/server.
  packages/solid/vite.config.mjs#L17-21packages/solid/tsconfig.test.json#L10-11
• Respect test-global interactions: client isolate:false, the MessageChannel replacement, and explicit scheduler resetting in the transition regression can affect scheduling-focused tests.
  packages/solid/vite.config.mjs#L23-28packages/solid/test/MessageChannel.ts#L1-9packages/solid/web/test/transition.spec.tsx#L17-23
• Avoid mistaking external adapters for local implementations: DOM, SSR, hyperscript, tagged-template, and universal expression engines are re-exported dependency code; fixes may require dependency-level investigation.
  packages/solid/web/src/client.ts#L1-1packages/solid/web/server/server.ts#L1-1packages/solid/h/src/hyperscript.ts#L1-1packages/solid/html/src/lit.ts#L1-1
• Keep downloaded integration execution separate from routine import checking: the default integration test uses test:imports, whereas test:integrations invokes a suite with downloads, shell commands, packing, and deletion.
  packages/test-integration/package.json#L4-8packages/test-integration/tests/downloaded.spec.ts#L24-58packages/test-integration/tests/downloaded.spec.ts#L71-99
• Follow the established formatting and TypeScript configuration: two-space indentation, semicolons, double quotes, no trailing commas, strict NodeNext resolution, preserved JSX, and declaration generation.
  .prettierrc#L1-8tsconfig.json#L1-12
• Release operations are explicit root scripts, and Changesets links solid-js with babel-preset-solid; publishing requires build/types and should not be conflated with local verification.
  package.json#L17-21.changeset/config.json#L3-9