[core] Running release:build twice causes errors #28359
Description
- The issue is present in the latest release.
- I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
Running the yarn release:build command on freshly checked-out sources works as intended. However, executing the same command for the second time fails with the following error:
Error: Command failed: yarn tsc -b E:\Development\MUI\material-ui\packages\mui-lab\tsconfig.build.json
error Command failed with exit code 2.
at ChildProcess.exithandler (child_process.js:319:12)
at ChildProcess.emit (events.js:376:20)
at maybeClose (internal/child_process.js:1055:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5) {
killed: false,
code: 2,
signal: null,
cmd: 'yarn tsc -b E:\\Development\\MUI\\material-ui\\packages\\mui-lab\\tsconfig.build.json',
stdout: '$ E:\\Development\\MUI\\material-ui\\node_modules\\.bin\\tsc -b E:\\Development\\MUI\\material-ui\\packages\\mui-lab\\tsconfig.build.json\n' +
"../mui-system/src/createTheme/createTheme.d.ts(3,41): error TS6305: Output file 'E:/Development/MUI/material-ui/packages/mui-system/build/createTheme/createSpacing.d.ts' has not been built from source file 'E:/Development/MUI/material-ui/packages/mui-system/src/createTheme/createSpacing.ts'.\r\n" +
"../mui-system/src/index.d.ts(139,42): error TS6305: Output file 'E:/Development/MUI/material-ui/packages/mui-system/build/createTheme/createSpacing.d.ts' has not been built from source file 'E:/Development/MUI/material-ui/packages/mui-system/src/createTheme/createSpacing.ts'.\r\n" +
"../mui-system/src/index.d.ts(140,41): error TS6305: Output file 'E:/Development/MUI/material-ui/packages/mui-system/build/createTheme/createSpacing.d.ts' has not been built from source file 'E:/Development/MUI/material-ui/packages/mui-system/src/createTheme/createSpacing.ts'.\r\n" +
'info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.\n',
stderr: 'error Command failed with exit code 2.\n'
}
Cleaning the projects before building (e.g. running yarn prebuild in individual packages' folders) seems to be a workaround (see #28319).
Expected Behavior 🤔
Building the projects several times in a row should not fail.
Steps to Reproduce 🕹
Steps:
- Check out fresh sources (or use
git clean -fxd) - Run
yarn release:buildin the repository root - Run
yarn release:buildin the repository root again
Your Environment 🌎
`npx @mui/envinfo`
System:
OS: Windows 10 10.0.19043
Binaries:
Node: 14.17.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
npm: 7.6.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 93.0.4577.63
Edge: Spartan (44.19041.1023.0), Chromium (93.0.961.47), ChromiumDev (95.0.1000.0)
npmPackages:
@emotion/react: ^11.4.1 => 11.4.1
@emotion/styled: ^11.3.0 => 11.3.0
@mui/codemod: 5.0.0-rc.1
@mui/core: 5.0.0-alpha.46
@mui/docs: 5.0.0-rc.1
@mui/envinfo: 2.0.1
@mui/icons-material: 5.0.0-rc.1
@mui/lab: 5.0.0-alpha.46
@mui/markdown: 5.0.0
@mui/material: 5.0.0-rc.1
@mui/material-next: 6.0.0-alpha.0
@mui/private-theming: 5.0.0-rc.1
@mui/styled-engine: 5.0.0-rc.1
@mui/styled-engine-sc: 5.0.0-rc.1
@mui/styles: 5.0.0-rc.1
@mui/system: 5.0.0-rc.1
@mui/types: 7.0.0-rc.1
@mui/utils: 5.0.0-rc.1
@mui/x-data-grid: 4.0.0
@mui/x-data-grid-generator: 4.0.0
@mui/x-data-grid-pro: 4.0.0
@mui/x-license-pro: 4.0.0
@types/react: ^17.0.20 => 17.0.20
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
styled-components: 5.3.1
typescript: ^4.4.3 => 4.4.3
This also happens on MacOS.