-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Path/baseUrl creates broken Type Definitions #21507
Comments
I am not sure i understand the intention behind your I tried running |
I have the same issue when removing I have tried
This makes sense as const xml_components_1 = require("file/xml-components"); Obviously it won't be able to find |
The compiler will not change your file path/import module name. what baseUrl tells the compiler is that at runtime all modules will be copied to this folder. AMD modules are usually distributed this way. if this is not your setup, do not use |
Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed. |
TypeScript Version: 2.6.2
Search Terms: npm, link, declarations, type definitions, awesome-typescript-loader, paths, baseUrl
I have tried to search for this, but couldn't find something similar, so I am asking 😄.
I am using
awesome-typescript-loader
to bundle my typescript project into onebuild/index.js
file:https://github.com/dolanmiu/docx/blob/master/webpack.config.js#L7-L8
I am using
compilerOptions.paths
to enable me to import from root:https://github.com/dolanmiu/docx/blob/master/tsconfig.json#L14-L18
I also have
declarations: true
:https://github.com/dolanmiu/docx/blob/master/tsconfig.json#L11
However, when I
npm link
, and use the library, I get the following error:file/media
packer
is an interfaceExpected behavior: Create typescript definitions without red underline errors
Actual behavior: Red underline errors, and error log
Related Issues:
#6496
Project:
https://github.com/dolanmiu/docx
The text was updated successfully, but these errors were encountered: