Load SolidStart init logging

[dahlia]

Summary

This fixes the SolidStart fedify init template so the generated src/logging.ts module is loaded from src/middleware/index.ts before Fedify handles requests.

The PR also adds a focused regression test in packages/init/src/webframeworks.test.ts to check that the generated SolidStart middleware imports the logging module.

Fixes #725

Tests

• deno check packages/init/src/webframeworks.test.ts
• hongdown --check CHANGES.md
• pnpm --filter @fedify/init test
• deno run -A packages/init/src/test/execute.ts init /tmp/fedify-init-725-solidstart -w solidstart -p npm -k in-memory -m in-process --dry-run
• mise run check:types
• git diff --check

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 209b9f4d-4de7-4a87-b2e9-654bd8cb2f49

📥 Commits

Reviewing files that changed from the base of the PR and between cb3394b and f7f2911.

📒 Files selected for processing (2)

• packages/init/src/templates/solidstart/src/middleware/index.ts.tpl
• packages/init/src/webframeworks.test.ts

---

📝 Walkthrough

Walkthrough

The SolidStart middleware template now imports the logging module as a side-effect before exporting the Fedify middleware. A test case validates that the generated middleware file includes this logging import, ensuring the logging configuration is wired into the framework at runtime.

Changes

Cohort / File(s)	Summary
SolidStart Middleware Template packages/init/src/templates/solidstart/src/middleware/index.ts.tpl	Added side-effect import of ../logging module to ensure logging configuration is initialized when the middleware loads.
Framework Initialization Tests packages/init/src/webframeworks.test.ts	Added SolidStart-specific test case that verifies the generated middleware file exists and contains the logging module import statement.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

component/integration

Suggested reviewers

• 2chanhaeng

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	Title 'Load SolidStart init logging' accurately describes the main change: adding logging module import to SolidStart middleware template.
Description check	✅ Passed	Description clearly explains the fix for SolidStart logging in the init template and references issue #725, with appropriate test commands.
Linked Issues check	✅ Passed	PR fully addresses the SolidStart objective from issue #725: imports logging module from middleware entry point before Fedify handles requests, with regression test.
Out of Scope Changes check	✅ Passed	All changes are scoped to SolidStart init template and its test; no unrelated modifications to other frameworks or components.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[dahlia]

@codex review

[gemini-code-assist]

Code Review

This pull request adds a SolidStart template to the @fedify/init package, including the addition of logging middleware and a new test case to verify its inclusion. The feedback suggests appending the .ts extension to the logging import path in both the template and the test suite to ensure Deno compatibility and maintain consistency across the project's templates.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🎉

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[2chanhaeng]

Great! 👍