-
Notifications
You must be signed in to change notification settings - Fork 28
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
Preventing /// <reference types="...
from showing up in declaration output
#248
Comments
Can you link me to where they say it's correct? Have we tested what happens if the addon itself includes a I wonder if tsc is smart enough to not do this if ember-source was using package.json exports to force these files to be private? Surely under those conditions it would be wrong to directly access them from typescript. |
Specifically:
I hadn't, because that would mean min-supported version would have to be The fix I've implemented is also not ideal, because I don't know what the consequences of For some papertrail / history, her are other occurrences of this problem: Starting back in August, 2023:
Also (duplicate issue reports) |
Last fix related to this problem here: ember-cli/ember-page-title#283
Not sure what to do, as TypeScript says the behavior (of including references) is correct, so that means we kinda have to work around it.
The text was updated successfully, but these errors were encountered: