Skip to content

Conversation

@heelrayner
Copy link
Owner

Summary

  • add PowerShell install and uninstall helpers so Windows users can set up or clean the app
  • document Windows usage alongside the existing macOS/Linux scripts in the README

Testing

  • Not run (not requested)

Codex Task

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ 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".

Comment on lines +71 to +75
const targetPath = normalize(join(base, target));
if (!targetPath.startsWith(base)) {
return base;
}
return targetPath;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Serve actual static assets instead of always returning index

Static asset requests currently get HTML because safeJoin is called with leading-slash pathnames (e.g. /styles.css), so join(publicDir, target) drops publicDir, targetPath.startsWith(publicDir) fails, and the function returns the directory. serveStatic then treats every request as a directory hit and falls back to index.html with text/html, meaning /styles.css or /assets/main.js are never served and the UI cannot load. Strip the leading slash or otherwise join paths so assets resolve under publicDir instead of always falling back to the SPA entry.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants