Scully build fails immediately in new project

🐞 Bug report

Description

I have built a fresh angular application and followed the scully docs on how to add scully and build a static site.

However when running npm run scully I get the following error

> scully

using plugins from folder "./scully"
Typescript error while compiling plugins. the error is:
error TS5042: Option 'project' cannot be mixed with source files on a command line.

💻Your Environment

Windows

💻Minimal reproduction steps

ng new my-app
cd ./my-app
ng add @scullyio/init
npm run build
npm run scully

Angular Version:

     _                      _                 ____ _     ___ 
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | | 
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | | 
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI: 10.1.3
Node: 12.18.3
OS: win32 x64

Angular: 10.1.3
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Ivy Workspace: Yes

Package                         Version
---------------------------------------------------------       
@angular-devkit/architect       0.1001.3
@angular-devkit/build-angular   0.1001.3
@angular-devkit/core            10.1.3
@angular-devkit/schematics      10.1.3
@angular/language-service       10.1.4
@schematics/angular             10.1.3
@schematics/update              0.1001.3
rxjs                            6.6.3
typescript                      4.0.3

Scully Version:

    "@scullyio/init": "^1.0.1",
    "@scullyio/ng-lib": "^1.0.0",
    "@scullyio/scully": "^1.0.0",

🔥 Exception or Error

> scully

using plugins from folder "./scully"
Typescript error while compiling plugins. the error is:
error TS5042: Option 'project' cannot be mixed with source files on a command line.

[AlexFBP]

Honestly this was the first time I had to move a whole project to another folder, just by having a space in the path…

However, yes, it doesn’t matter so much after all. What I’m saying is that I don’t think that it is directly related to Scully, but to one of its dependencies, as that error appears not only with Scully but in other places, projects where Typescript is used…

Needless to say I’m a newbie on Angular 😅 , I tried (not so much TBH) to seek a way to fix this (for me it has no sense that a whole project gets “killed” by just having space(s) in its path, like as I were using old development tools) but I “successfully failed” 😅

[SanderElias]

@AlexFBP I’m on Ubuntu 20. Spaces in pathnames is an issue in many tools. What you are seeing is a similar yet different issue. Perhaps just don’t use spaces in path-names 😉 I took a quick look, and it seems to be something around typescript that goes haywire. When you think this is important enough, please open a new ticket.