Skip to content

deno doc --lint complaints about a private type when it's public, but in a different entrypoint #25145

Answered by skybrian
skybrian asked this question in Q&A
Discussion options

You must be logged in to vote

To partially answer my own question, this seems to have something to do with using relative imports internally somewhere for public symbols? I changed some internal imports to start with "@skybrian/repeat-test" and it went away.

Edit: It came back for a while, and then went away again. This is looking more like a non-deterministic bug. Maybe a caching issue?

Edit 2: Definitely nondeterministic. I created a bug: #25188

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by skybrian
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant