logdna / logdna/logger-node

Files missing in dist package

Open
#92 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
36
Forks
11
PR merge metrics
No merged PRs in 30d

Description

When compiling TSC writes the following errors:

WARNING in ../../node_modules/@logdna/logger/node_modules/agent-base/dist/helpers.js
Module Warning (from ../../node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/zzz/node_modules/@logdna/logger/node_modules/agent-base/src/helpers.ts' file: Error: ENOENT: no such file or directory, open '/zzz/node_modules/@logdna/logger/node_modules/agent-base/src/helpers.ts'

WARNING in ../../node_modules/@logdna/logger/node_modules/agent-base/dist/index.js
Module Warning (from ../../node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/zzz/node_modules/@logdna/logger/node_modules/agent-base/src/index.ts' file: Error: ENOENT: no such file or directory, open '/zzz/node_modules/@logdna/logger/node_modules/agent-base/src/index.ts'

WARNING in ../../node_modules/@logdna/logger/node_modules/https-proxy-agent/dist/index.js
Module Warning (from ../../node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/zzz/node_modules/@logdna/logger/node_modules/https-proxy-agent/src/index.ts' file: Error: ENOENT: no such file or directory, open '/zzz/node_modules/@logdna/logger/node_modules/https-proxy-agent/src/index.ts'

WARNING in ../../node_modules/@logdna/logger/node_modules/https-proxy-agent/dist/parse-proxy-response.js
Module Warning (from ../../node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/zzz/node_modules/@logdna/logger/node_modules/https-proxy-agent/src/parse-proxy-response.ts' file: Error: ENOENT: no such file or directory, open '/zzz/node_modules/@logdna/logger/node_modules/https-proxy-agent/src/parse-proxy-response.ts'

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the TSC compilation and inspect the dist files and source-map references for agent-base and https-proxy-agent under @logdna/logger. Trace how the package is assembled, then verify that the published package no longer produces missing-source-map warnings for the listed files.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.