Cannot read property 'search' of null

🐞 Bug report

Description

ng add @scullyio/init finished with the error Cannot read property 'search' of null and scully.<projectName>.config.ts file is not created in the project

🔬 Minimal Reproduction

1. ng add @scullyio/init

💻Your Environment

Angular Version:

Angular CLI: 9.1.12
Node: 14.15.1
OS: win32 x64

Angular: 9.0.4
... common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router
Ivy Workspace: Yes

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.901.12
@angular-devkit/build-angular      0.901.9
@angular-devkit/build-optimizer    0.901.9
@angular-devkit/build-webpack      0.901.9
@angular-devkit/core               9.0.4
@angular-devkit/schematics         9.0.4
@angular/animations                9.1.12
@angular/cdk                       9.2.4
@angular/cli                       9.1.12
@angular/fire                      5.4.2
@angular/flex-layout               9.0.0-beta.31
@angular/http                      4.4.6
@angular/material                  9.2.4
@angular/material-moment-adapter   7.3.7
@angular/youtube-player            11.0.0
@ngtools/webpack                   9.1.9
@nguniversal/express-engine        7.0.2
@schematics/angular                9.0.4
@schematics/update                 0.901.12
rxjs                               6.5.4
typescript                         3.7.5
webpack                            4.42.0

Scully Version:

"@scullyio/init": "^1.0.1"

🔥 Exception or Error

Installing packages for tooling via npm.
Installed packages for tooling via npm.
Cannot read property 'search' of null

[alessandro-tucci-visiontech]

My two cents: as per what I found while dealing with this analoguous issue (#1402) , it may be due to a couple of Scully’s implicit requirements:

1. @angular/core shall be explicitly listed in the dependencies section of your package.json file, e.g.

  "dependencies": {
    "@angular/core": "~11.2.14",
    [..]
  }

1. Your package.json file shall contain a scripts section. If you don’t have any script to list, declare it empty,

{
  [..]
  "dependencies": {
    [..]
  },
  "devDependencies": {
    [..]
  },
  "scripts": {}
}

[SanderElias]

Iḿ closing this, as I believe this problem is solved now. If I’m mistaken, let m know and I will reopen it