feat: add support for none config in dotfolder

[anshumanv]

What kind of change does this PR introduce?
feat

Did you add tests for your changes?
Yes

If relevant, did you update the documentation?
NA

Summary

• Add support for reading none config from dotfolder
• Add relevant tests

Does this PR introduce a breaking change?
No

Other information
No

[alexander-akait]

Can we add tests where we have multiple configuration and load them based on mode?

[anshumanv]

Can we add tests where we have multiple configuration and load them based on mode?

Config resolves doesn't respect mode, will add the support

[alexander-akait]

Can we create test where we have

• .webpack/webpack.config.developmen.js
• webpack.config.developmen.js
• webpack.config.js

We need test what we load the right configuration

[anshumanv]

Yes, in near future @evilebottnawi 👍

[anshumanv]

@evilebottnawi added 👍

[alexander-akait]

So we prefer webpack.config.develoment.js over .webpack/webpack.config.development.js?

[anshumanv]

So we prefer webpack.config.develoment.js over .webpack/webpack.config.development.js?

Yes

[alexander-akait]

@webpack/cli-team we need small discussion about it, should we prefer config from .webpack directory over root configuration or not?

[rishabh3112]

.webpack/* as this now what we intend to be the default directory for configurations by design.

[anshumanv]

Seems fair

[anshumanv]

Updated

[webpack-bot]

@anshumanv Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@snitin315 Please review the new changes.