Open zhangxuan615 opened 2 months ago
I'm guessing rollup is printing something to stderr. Rush considers an operation successful with warnings if it exits with code 0 but also prints to stderr.
You should be able to see what specifically is getting printed to stderr by looking at the *.error.log
file in the project's rush-logs
folder (assuming you're on a recent version of Rush) or in the project root.
@iclanton I tested it with a simplest demo by running rush init
, and the version of rush I'm using is 5.129.6
:
*.error.log
file.
rollup -c
directly in the sub-package directory.
Summary
The console always prints a warning tip(
SUCCESS WITH WARNINGS...
) if a sub-package has a build command: rollup -c, when I runrush rebuild
in the root directory. What's even weirder is that it just says there's a warning, but it doesn't provide any details about the warning.If I run directly the command (rollup -c) in the sub-package directory, no warning will be printed.
So, from my opinion, I just think there is incompatibility in
rush
androllup
.Repro steps
export const a = 1; console.log("test:", a)
module.exports = { input: "src/index.js" }
run rebuild
in the root directory.Details