michaltalaga

further investigation shows breaking change was introduced in https://github.com/nestjs/nest-cli/releases/tag/10.2.0

narrowed it down to: https://github.com/michaltalaga/nestjs-cli-i18n-issue git clone npm install // this will use "@nestjs/cli": "10.2.0", npm run start:dev it will fail git clone // change to "@nestjs/cli": "10.1.18", npm install...

may be a red herring but it has something to do with nest-cli.json

that is possible. it worked till 10.1.18 - no issues tho if I use the default nest-cli.json { "$schema": "https://json.schemastore.org/nest-cli", "collection": "@nestjs/schematics", "sourceRoot": "src", "compilerOptions": { "deleteOutDir": true } }...

tried out. no luck

to recap: starting in version 10.2.0 following nest-cli.json fails on windows ``` { "language": "ts", "collection": "@nestjs/schematics", "sourceRoot": "src", "compilerOptions": { "assets": [ "**/*.html", "**/*.otf", "i18n/**/*", "**/*.json" ] } }...

I have implemented my own fix, but can we please have it fixed in the official NuGet package?

I ended up changing 2 files: in Raspberry.System/Processor.cs I've added: ``` /// /// The Raspberry Pi processor. /// public enum Processor { /// /// Processor is unknown. /// Unknown, ///...

That is the very reason I haven't created a pull request. I'm no expert in this. Did not want to break some other implementations. I just know my RPi3 worked...