You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working #1654 I discovered that we get strange text on stderr when running the pepr build command with the --no-embed flag:
The module still appears to build (successfully, maybe..?).
The build command returns an exit code of "0".
The stdout stream comes back empty.
The stderr stream comes back with containing an error like: "Error: Cannot find module [...])
This should be investigated. Current behavior codified in (upcoming) integration test for the pepr build cli:
/integration/cli/build.noembed.test.ts : build > builds a module > for use as a library > builds
Definition of Done
figure out whether this is a "real" error or just a matter of test setup / config, and
fix the error (if it is one).
The text was updated successfully, but these errors were encountered:
btlghrants
changed the title
--no-embed flag writes to stderr stream even when successful
--no-embed flag writes stderr stream with exitcode 0
Jan 14, 2025
btlghrants
changed the title
--no-embed flag writes stderr stream with exitcode 0
"pepr build --no-embed" flag writes stderr stream with exitcode 0
Jan 14, 2025
cmwylie19
changed the title
"pepr build --no-embed" flag writes stderr stream with exitcode 0
[SPIKE] - "pepr build --no-embed" flag writes stderr stream with exitcode 0
Jan 15, 2025
Background
While working #1654 I discovered that we get strange text on stderr when running the
pepr build
command with the--no-embed
flag:The module still appears to build (successfully, maybe..?).
The build command returns an exit code of "0".
The stdout stream comes back empty.
The stderr stream comes back with containing an error like: "Error: Cannot find module [...])
This should be investigated. Current behavior codified in (upcoming) integration test for the
pepr build
cli:Definition of Done
The text was updated successfully, but these errors were encountered: