-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Errors when type definition path is a subpath of a file in files
#57
Comments
Thanks for posting this. Will have a look :). |
@SamVerschueren Friendly ping :) This is quite annoying because I cannot put the declarations file in the |
I'll see if I can fix this. Shouldn't be that hard. |
So I looked into this, and this is already fixed somewhat, see #69 for more information. For instance, the following {
"name": "foo",
"files": [
"out"
],
"types": "out/index.d.ts"
} What doesn't work however, is this {
"name": "foo",
"files": [
"out"
],
"types": "out"
} When looking at the specs of the Does this fix the issue for both of you @szmarczak and @posva? |
I'm going to close this, feel free to create a new issue or ask me to reopen it if it's not working as expected. |
Yep, it's working as expected. Sorry I haven't told you before, I totally forgot 🙈 |
If the type definition file is in a subfolder of a path included in
files
,tsd
will error this message:sample
package.json
file:Creating an empty file
dist/src/index.d.ts
alongside this package.json file should be enough to reproduce it 🙂As a workaround, including
dist/src
infiles
works just fineThe text was updated successfully, but these errors were encountered: