mkamrani
commented
2 years ago I couldn't reproduce it on my Mac with version 0.4.0, would be good to what's the OS of the machine error happened. I'm suspecting this is a Window thing.
Closed mkamrani closed 6 months ago
mkamrani
commented
2 years ago I couldn't reproduce it on my Mac with version 0.4.0, would be good to what's the OS of the machine error happened. I'm suspecting this is a Window thing.
TomCockram
commented
2 years ago Yeah, this was performed on windows.
mkamrani
commented
2 years ago Sorry if this has taken some time, I'm using mac. I just started a Windows ec2 instance to be able to debug it.
name: test stack: frontend framework: Angular pm: Yarn uiFramework: Bootstrap testFramework: Default linting: Prettier
Creating the project test ... yarn global v1.22.15 [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... [4/4] Building fresh packages... success Installed "@angular/cli@13.3.4" with binaries:
node --trace-warnings ...to show where the warning was created) (node:32124) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:32124) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.