Lars Kappert
Lars Kappert
That looks a bit odd indeed. Draft releases should have the notes handled the same. I've tried https://github.com/release-it/release-it/blob/main/docs/github-releases.md#update-the-latest-release a few times (a while ago) and this worked well. In general...
Btw the config you're showing doesn't show anything specific to release-it?
> After this new pre-release ones are failing as tags are technically invalid according to semver. Although tags don't require semver validness, allowing this in a plugin might cause all...
Closing due to inactivity.
Thanks for report. That's correct [according to the Node.js docs](https://nodejs.org/api/packages.html#subpath-patterns) and honestly I'm a bit baffled by it: > \* maps expose nested subpaths as it is a string replacement...
Just saying, the generic (and intended) solution to this is to add `entry` patterns to your knip config manually: ```json { "entry": ["./src/public/{a,b}/index.ts"] } ``` At this point this feels...
Understood, but this is a good example of static analysis versus runtime behavior and there are tradeoffs to be considered.
There's a known issue as described above. Also, feel free to create a reproduction I could look into.
@acidoxee Feel free to create a separate issue. The reproduction is incomplete and then still I can't reproduce incorrect behavior.
For this to happen a few things had to come together, in short: - Introduction of [`inputs` with `Options`](https://knip.dev/guides/writing-a-plugin#inputs) so we can start specifying when exports of entry files should...