Warning on running nest api
See original GitHub issue##Current Behavior
It shows an warning when I run nx serve api
in a recently created workspace with nest and angular.
WARNING in ./apps/api/src/app/app.controller.ts 18:56-63
"export 'Message' was not found in '@test/api-interfaces'
WARNING in ./apps/api/src/app/app.controller.ts 18:83-90
"export 'Message' was not found in '@test/api-interfaces'
Expected Behavior
I expected it to work without warnings when I create it.
Steps to Reproduce
You should run:
npx create-nx-workspace test
Select the options:
angular-nest [a workspace with a full stack application (Angular + Nest)]
Application name test
Default stylesheet format SASS(.scss) [ http://sass-lang.com ]
Default linter TSLint [ Used by Angular CLI ]
Go to the directory
cd test
Use:
nx serve api
Environment
File contents:
/libs/api-interfaces/src/index.ts
export * from './lib/api-interfaces';
/libs/api-interfaces/src/lib/api-interfaces.ts
export interface Message {
message: string;
}
> NX Report complete - copy this into the issue template
nx : Not Found
@nrwl/angular : 10.3.0
@nrwl/cli : 10.3.0
@nrwl/cypress : 10.3.0
@nrwl/eslint-plugin-nx : Not Found
@nrwl/express : Not Found
@nrwl/jest : 10.3.0
@nrwl/linter : 10.3.0
@nrwl/nest : 10.3.0
@nrwl/next : Not Found
@nrwl/node : 10.3.0
@nrwl/react : Not Found
@nrwl/schematics : Not Found
@nrwl/tao : 10.3.0
@nrwl/web : Not Found
@nrwl/workspace : 10.3.0
typescript : 4.0.3
It happened with versions 6.14.7 and 10.3.0.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:12
- Comments:7 (1 by maintainers)
Top Results From Across the Web
What different HVAC monitoring alerts mean - Google Nest Help
It identifies heating failures by monitoring changes in your indoor temperature while your system is heating. If those changes are different than what...
Read more >Thermostat API - Nest Developers
Warning: This data value has been deprecated. Use eco_temperature_low_c instead. Minimum away temperature, displayed in half degrees Celsius (0.5°C). Details.
Read more >SchematicsNestApplication schema warning on running `nest ...
This is a change between @angular-devkit/ between v11 and v12. It's more for the Nest schematics to be updated than a problem with...
Read more >faulty warning message... "Your heating system fai...
... warning in the middle of the night for a new nest thermostat. ... The heat wasn't called for or running when the...
Read more >Logger | NestJS - A progressive Node.js framework
Nest comes with a built-in text-based logger which is used during application bootstrapping and several other circumstances such as ...
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
@inglkruiz Thanks for your comment. It led to the solution.
I mean that instead of
import {MyCustom} from "...";
, usingimport type {MyCustom} from "...";
solves the problem.@Guilherhast after reading this article and tried the solution proposed the warnings were gone > https://medium.com/javascript-in-plain-english/leveraging-type-only-imports-and-exports-with-typescript-3-8-5c1be8bd17fb also you might want to check this https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html#type-only-imports-and-export Found solutions here https://github.com/webpack/webpack/issues/7378