Use this to load modules whose location is specified in the
paths section of
tsconfig.json when using webpack. This package provides the functionality of
the tsconfig-paths package but
as a webpack plug-in.
How to install
NOTE: If you are using webpack 4 you need to use version >= 3.0.0 (which is aso backwards compatible with webpack 3).
yarn add --dev tsconfig-paths-webpack-plugin
npm install --save-dev tsconfig-paths-webpack-plugin
How to use
In your webpack config add this:
const TsconfigPathsPlugin = ;moduleexports =...resolve:plugins: /*configFile: "./path/to/tsconfig.json" */...
Notice that the plugin is placed in the
resolve.pluginssection of the configuration.
tsconfig-paths-webpack-pluginis a resolve plugin and should only be placed in this part of the configuration. Don't confuse this with the plugins array at the root of the webpack configuration object.
This package has typescript typings included. If your webpack config is using typescript, you can use this syntax to import the default export:
Or you can use this syntax to import the named export:
configFile (string) (default='tsconfig.json')
Allows you to specify where to find the TypeScript configuration file.
You may provide
- just a file name. The plugin will search for the filename using the built-in
logic in the
tsconfig-pathspackage. The search will start at
- a relative path to the configuration file. It will be resolved relative to
- an absolute path to the configuration file.
The use of
cwdas default above is not optimal but we've found no better solution yet. If you have a suggestion please file an issue.
extensions (string) (default=[".ts", ".tsx"])
An array of the extensions that will be tried during resolve. Ideally this would be the same as the extensions from the webpack config but it seems resolver plug-ins does not have access to this infomration so you need to specify it again for the plugin.
baseUrl (string) (default=undefined)
This allows you to override the
baseUrl found in tsconfig.json. The baseUrl specifies from which directory
paths should be resolved. So this option enabled you to resolve from anhother directory than the one where tsconfig.json is located. This can be useful if you want to use webpack with
tsc --watch instead of a typescript loader. If this option is
undefined then the
baseUrl from tsconfig.json will be used.
mainFields (string) (default=["main"])
An array of the field names that should be considered when resolving packages. Ideally this would be the same as the mainFields from the webpack config but it seems resolver plug-ins does not have access to this infomration so you need to specify it again for the plugin.
silent (boolean) (default=false)
If true, no console.log messages will be emitted. Note that most error messages are emitted via webpack which is not affected by this flag.
logLevel (string) (default=warn)
error which limits the log output to the specified
log level. Beware of the fact that errors are written to stderr and everything
else is written to stderr (or stdout if logInfoToStdOut is true).
colors (boolean) (default=true)
false, disables built-in colors in logger messages.
logInfoToStdOut (boolean) (default=false)
This is important if you read from stdout or stderr and for proper error handling. The default value ensures that you can read from stdout e.g. via pipes or you use webpack -j to generate json output.
How to test
To run the provided example:
This project uses work done in the awesome-typescript-loader.