Export interfaces at the root level

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

The Provider interface has to be imported from a submodule:

import { Provider } from '@nestjs/common/interfaces/modules/provider.interface';
export const requestSchedulerProvider: Provider = {....}

Expected behavior

The interface should be exposed at it’s root level

import { Provider } from '@nestjs/common';

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

[tslint] Submodule import paths from this package are disallowed; import from the root instead (no-submodule-imports)

Reasoning for this rule from palantir: “Submodules of some packages are treated as private APIs and the import paths may change without deprecation periods. It’s best to stick with top-level package exports.”

Environment

Nest version: 5.0.0-beta.7

[kamilmysliwiec]

Thanks for reporting. I’ll fix it in the next RC. Btw. 5.0.0-rc.1 is available already

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.