Skip to content

Error: Option "rootDir" is not defined #165

@hemedah101

Description

@hemedah101

I'm submitting a...


[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Iam trying to follow the example here https://trilon.io/blog/deploy-nestjs-azure-functions
for azure functions deployment, however I keep getting this error


$ nest add @nestjs/azure-func-http
√ Installation in progress... ☕
Error: Option "rootDir" is not defined.
    at C:\Users\hemed\Desktop\_coreteck\gray\pos-system-backend\node_modules\@angular-devkit\schematics\src\rules\template.js:85:27     
    at C:\Users\hemed\Desktop\_coreteck\gray\pos-system-backend\node_modules\@angular-devkit\schematics\src\rules\base.js:109:30        
    at C:\Users\hemed\.npm-global\node_modules\@nestjs\cli\node_modules\@angular-devkit\schematics\src\tree\host-tree.js:233:13
    at C:\Users\hemed\.npm-global\node_modules\@nestjs\cli\node_modules\@angular-devkit\schematics\src\tree\host-tree.js:41:59
    at Array.forEach ()
    at HostDirEntry.visit (C:\Users\hemed\.npm-global\node_modules\@nestjs\cli\node_modules\@angular-devkit\schematics\src\tree\host-tree.js:41:43)
    at HostCreateTree.visit (C:\Users\hemed\.npm-global\node_modules\@nestjs\cli\node_modules\@angular-devkit\schematics\src\tree\host-tree.js:232:19)
    at C:\Users\hemed\Desktop\_coreteck\gray\pos-system-backend\node_modules\@angular-devkit\schematics\src\rules\base.js:105:14        
    at MergeMapSubscriber.project (C:\Users\hemed\Desktop\_coreteck\gray\pos-system-backend\node_modules\@angular-devkit\schematics\src\rules\call.js:74:24)
    at MergeMapSubscriber._tryNext (C:\Users\hemed\Desktop\_coreteck\gray\pos-system-backend\node_modules\@angular-devkit\schematics\node_modules\rxjs\internal\operators\mergeMap.js:69:27)

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment


Nest version: 7.0.3

 
For Tooling issues:
- Node version: 12.14  
- Platform:  Windows 

Others:

package manager: yarn

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions