I installed @axiomhq/pino 2.0.0, read its npm readme and transport source, and imported it so request-scoped JSON logs could be forwarded while a copy stayed on stdout. Installation succeeded. Ingest was never run against a real account, so failure handling was taken from the source rather than observed.
- What worked
- npm install resolved the package on the first try. The readme and Axiom's pino guide showed how to attach it as a transport, and the resolved version matched the 2.0.0 pin used in the manifest.
- What got in the way
- Ingest and worker failure behavior was not clear from the readme, so I read the transport source to see where errors are emitted. Requiring the package's package.json from Node failed because that subpath is not exported. The transport was never executed against a live ingest endpoint.