YR Chen

Met the same problem. There should be a way to support Basic Authentication, instead of letting `jwt-auth` totally shadow it.

As for me, I recommend to implement a whole new router within this repo, as a new library or a non-default part of `RoutingKit` itself. How do you think @Sorix...

I supposed #414 to only _allow more package to be displayed_, and didn’t expect this. Will take some time to look into it.

Given the fix I believe the real cause is #382 – hopefully we can avoid this being broken by adding a new test case.

@adam-fowler Do you think apple/swift-syntax is a better choice? (~10MB download)

I was a bit hesitated because SwiftSyntax is under heavy development and this is subject to change. [SwiftProtobuf](https://github.com/apple/swift-protobuf) is another choice with ~25MB download.

Wait, we need to support Swift 5.4 CI, right? Then SwiftSyntax and AsyncAlgorithms aren't applicable. Is SwiftProtobuf something acceptable?

Can we track `swift run` state as a language status item? This looks more Xcode-like and easier to control.

Seems to duplicate https://github.com/swift-server/vscode-swift/issues/416#issuecomment-1245374734? It should be a Swift Driver bug which is pure toolchain-related. Once the Swift Driver bug is fixed, we should be able to use the feature.

I guess the not-founds are related to `swiftc` not recognizing Clang’s header include path. This is what I get now: ``` administrator@iZslngp7ujsw3eZ C:\Users\Administrator\Developer\swift-atomics>swift build -Xswiftc -I -Xswiftc C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\lib\clang\13.0.0\include Building for...