test(solid-query-devtools/devtools{,Panel}): add tests for the non-development fallback#10848
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughThe PR adds two Vitest tests that assert ChangesProduction environment null-return tests
Possibly related PRs
Poem
🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit 52e1b7f
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version Preview2 package(s) bumped directly, 23 bumped as dependents. 🟩 Patch bumps
|
size-limit report 📦
|
…velopment fallback
52e1b7f to
6962c9e
Compare
🎯 Changes
Add a non-development fallback test case to both
SolidQueryDevtoolsandSolidQueryDevtoolsPanel, mirroring the matrix that already exists for the React, Preact, and Vue adapters.Unlike React/Preact/Vue, Solid does not switch on
process.env.NODE_ENV. Theindex.tsxof@tanstack/solid-query-devtoolsreadsisDevfromsolid-js/web, which is a build-time constant, so the usualvi.stubEnv('NODE_ENV', 'production')approach has no effect here. The new case swapsisDevtofalsevia per-testvi.doMock('solid-js/web', ...)and dynamically imports the module to exercise the fallback branch.✅ Checklist
🚀 Release Impact
Summary by CodeRabbit