You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2019. It is now read-only.
Switched from ts-loader and run into inconvenience with typescript config files.
The problem is that config file is searched in the root directory for each entry despite its path.
The question is is it possible to make awesome-typescript-loader search config in the resource directory like ts-loader does?
Example:
Some directories in the project have their own tsconfig.json and each of them has corresponding entry point in the webpack config (or configs). To make awesome-typescript-loader use the right config, you have to specify config path for every entry which often means duplication of module/module.rules options.
Hello guys!
Switched from
ts-loader
and run into inconvenience with typescript config files.The problem is that config file is searched in the root directory for each
entry
despite its path.The question is is it possible to make
awesome-typescript-loader
search config in the resource directory likets-loader
does?Example:
Some directories in the project have their own
tsconfig.json
and each of them has corresponding entry point in thewebpack
config (or configs). To makeawesome-typescript-loader
use the right config, you have to specify config path for everyentry
which often means duplication ofmodule
/module.rules
options.Project structure:
webpack.config.js:
Technically, this can be done with something like changing line
to
but is there any reason why this cannot / not intended to be done? I can open a PR myself if it's fine.
The text was updated successfully, but these errors were encountered: