Add config option to specify additional headers for serve

[oberien]

I'm using webworkers (based on #285) and want to use SharedArrayBuffer. That requires setting the headers Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp. To allow this configuration during development with trunk serve, I added a config option which allows specifying any number of header-value pairs, which are included in responses.

Checklist

• [x] Updated CHANGELOG.md describing pertinent changes.
• [ ] Updated README.md with pertinent info (may not always apply).
• [ ] Updated site content with pertinent info (may not always apply).
• [x] Squash down commits to one or two logical commits which clearly describe the work you've done. If you don't, then Dodd will 🤓.

[iTitus]

Is there any update on this? I'd like to add CORS headers in my local dev env.

[oberien]

Thanks for the review. Unfortunately the changes have become pretty stale. I rebased and needed to completely change up the implementation. It works with the new ServeDir instead of the custom endpoint implementation now.

This time I ran rustfmt, so the imports should be in the correct order :)

[vitvakatu]

Hi, @thedodd. Is anything blocking this PR? I also faced #414 in my project. I overlooked this PR and even prepared my own. (available here, the approach is slightly different, I also updated docs and added an example)

I'd love to see this merged and released. It's quite a simple feature that helps tremendously.

[SeanOMik]

I also would love to see this merged. It looks like GitHub is saying that this branch is out-of-date with the base branch. I'll be willing to try to rebase it to the master and make other changes if needed.

[oberien]

Rebased to the latest master. Is there anything else I can do to help move this PR along? (The 2 clippy lints don't affect code I changed.)

[chaosprint]

Thanks for this PR. Look forward to its progress.

[Cornul11]

Are there any updates on the possibility of merging this to the upstream?

[github-actions[bot]]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[ctron]

I merged this into trunk-ng, if it looks good for the next few days, it should be released as 0.17.11.

It would be great if any of you could test this feature specifically. You need to install trunk-ng from git for doing so: cargo install --git https://github.com/ctron/trunk --branch trunk-ng

[oberien]

I tested trunk-ng and it seems to work just fine. I can't tell a difference in behaviour between my branch and trunk-ng.

[ctron]

This is now released with trunk-ng 0.17.11

[github-actions[bot]]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[oberien]

This PR is not stale. The feature is used by several people and has even been integrated into trunk-ng.

[ctron]

This was brought back to trunk with PR https://github.com/trunk-rs/trunk/pull/623 and it should be part of the next release of trunk too.

[ctron]

This was released with trunk 0.18.0.