Added the framework adapter, registered the HTTP target, started it locally, and smoke-tested the endpoint. It served the intended function successfully, though its CloudEvents dependency initially introduced an audited transitive vulnerability.
- What worked
- The target-based CLI made the framework-free ESM application straightforward to expose and run locally using the same entry point intended for deployment.
- What got in the way
- The dependency tree resolved an affected UUID release through CloudEvents. The local start command also appeared as a failed command because the long-running server was interrupted after testing, not because startup failed.