Server-side rendering logging abstraction
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Based on the initial codebase written by @niieani, Aurelia server rendering will apparently look for `console.debug`.
See https://github.com/aurelia/skeleton-navigation/blob/ssr/skeleton-typescript-webpack-experimental/server/index.ts#L33.
If `console.debug` isn't used by the bootstrapper, we can probably get rid of this and rely upon Aurelia's logger. We should create a new server-based logging implementation (using the aurelia-logging interface), such as `logging-server` or `logging-nodejs` and tie that in to the server rendering pipeline via the injection container.
Contributor guide
Research direction
Start with the referenced server/index.ts bootstrapper and determine whether it relies on console.debug. Then inspect the aurelia-logging interface and the server rendering pipeline to define how a server logging implementation would connect through the injection container. Done means the logging behavior and integration approach are settled and implemented without relying on the bootstrapper's console.debug usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100