Copy Plugin errors out with Nx 10.1.0
See original GitHub issueCurrent Behavior
Running NestJS backend with Nx 10.1.0 errors out with the following error:
[error] ValidationError: Invalid options object. Copy Plugin has been initialized using an options object that does not match the API schema.
- options.patterns should be an non-empty array.
at validate (/Users/chautran/Code/Projects/@nartc/jira-clone-angular/ngvn/node_modules/schema-utils/dist/validate.js:96:11)
at new CopyPlugin (/Users/chautran/Code/Projects/@nartc/jira-clone-angular/ngvn/node_modules/copy-webpack-plugin/dist/index.js:24:30)
at Object.getBaseWebpackPartial (/Users/chautran/Code/Projects/@nartc/jira-clone-angular/ngvn/node_modules/@nrwl/node/src/utils/config.js:89:43)
at Object.getNodeWebpackConfig (/Users/chautran/Code/Projects/@nartc/jira-clone-angular/ngvn/node_modules/@nrwl/node/src/utils/node.config.js:40:18)
at MapSubscriber.project (/Users/chautran/Code/Projects/@nartc/jira-clone-angular/ngvn/node_modules/@nrwl/node/src/builders/build/build.impl.js:28:36)
at MapSubscriber._next (/Users/chautran/Code/Projects/@nartc/jira-clone-angular/ngvn/node_modules/rxjs/internal/operators/map.js:49:35)
at MapSubscriber.Subscriber.next (/Users/chautran/Code/Projects/@nartc/jira-clone-angular/ngvn/node_modules/rxjs/internal/Subscriber.js:66:18)
at MapSubscriber._next (/Users/chautran/Code/Projects/@nartc/jira-clone-angular/ngvn/node_modules/rxjs/internal/operators/map.js:55:26)
at MapSubscriber.Subscriber.next (/Users/chautran/Code/Projects/@nartc/jira-clone-angular/ngvn/node_modules/rxjs/internal/Subscriber.js:66:18)
at /Users/chautran/Code/Projects/@nartc/jira-clone-angular/ngvn/node_modules/rxjs/internal/util/subscribeToPromise.js:7:24
Expected Behavior
Should work.
10.0.13 worked fine.
Steps to Reproduce
https://github.com/angular-vietnam/jira-clone-angular/tree/feature/github-signin/ngvn The issue can be reproduced using this repo.
- Clone the repo
- Check out branch feature/github-signin
cd ngvn
- Update nx to 10.1.0 and install dependencies
npm run start:api
Error will show
Failure Logs
Log is provided above.
Environment
> NX Report complete - copy this into the issue template
nx : Not Found
@nrwl/angular : 10.1.0
@nrwl/cli : 10.1.0
@nrwl/cypress : 10.1.0
@nrwl/eslint-plugin-nx : Not Found
@nrwl/express : Not Found
@nrwl/jest : 10.1.0
@nrwl/linter : 10.1.0
@nrwl/nest : 10.1.0
@nrwl/next : Not Found
@nrwl/node : 10.1.0
@nrwl/react : Not Found
@nrwl/schematics : Not Found
@nrwl/tao : 10.1.0
@nrwl/web : Not Found
@nrwl/workspace : 10.1.0
typescript : 3.9.7
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Bug listing with status UNCONFIRMED as at 2022/12/24 17 ...
... Bug:382827 - "sys-apps/portage-2.1.10.11 crashes with confusing error when out of memory: TypeError: an integer is required" status:UNCONFIRMED ...
Read more >storybook missing class properties transform. - You.com
On start up I'm getting a bunch of Syntax Error: Missing class properties transform errors. However, it looks like @babel/plugin-proposal-class-properties ...
Read more >Writing R Extensions - The Comprehensive R Archive Network
Permission is granted to copy and distribute translations of this manual into another language, ... However, some common errors are worth pointing out...
Read more >OpenAM 13 > Developer's Guide - ForgeRock Backstage
This guide demonstrates how to implement such plugins. Custom OAuth 2.0 scopes plugins define how OpenAM, when playing the role of authorization server,...
Read more >Open Source Used In webexdevhub 1.0.0 - Cisco
1.342 @babel/plugin-transform-duplicate-keys 7.16.7 ... 1.615 csstools-normalize-css 10.1.0 ... 1.876 @aws-sdk/service-error-classification 3.13.1.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As a workaround you can add an empty assets folder to each affected project and reference it in the build options inside angular.json
Seems creating a file in the fake assets folder is also needed.