chore: bump version

[hiwllc]

[skip ci]

[netlify]

✅ Deploy Preview for uselessdev-datepicker ready!

Name	Link
🔨 Latest commit	6b757e2
🔍 Latest deploy log	https://app.netlify.com/sites/uselessdev-datepicker/deploys/66aab33c14de1a0007d8588a
😎 Deploy Preview	https://deploy-preview-85--uselessdev-datepicker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Philzen]

@uselessdev I'm so sorry, but just trying out the v2.8.0 release in our project i'm getting:

web | Failed to resolve entry for package "@uselessdev/datepicker". The package may have incorrect main/module/exports specified in its package.json.
web | 12:22:51 AM [vite] Internal server error: Failed to resolve entry for package "@uselessdev/datepicker". The package may have incorrect main/module/exports specified in its package.json.
web |   Plugin: vite:import-analysis

Bottom line – project cannot be compiled at all using v2.8.0 as a dependency.

Using "@uselessdev/datepicker": "https://github.com/Philzen/datepicker.git#commit=097e011ed9df0febb2f219ea8c18f8b5d303c143", in the project's package.json works fine though (at least locally, on CI currently poses a challenge due to a yarn bug i'm still trying to wrap my head around, but that should be unrelated to the problem at hand).

[Philzen]

@uselessdev just rm -rfed the node_modules folder, did a clean install and found that the 2.8.0 release does not ship any code at all as it does not include a dist/-folder (and furthermore the package.json does not seem to include the changes from #84).

[hiwllc]

oh I probaly forget something, just a moment

[hiwllc]

@Philzen can you try with v2.8.1 and let me know if it works

[Philzen]

@Philzen can you try with v2.8.1 and let me know if it works

Happy to report v2.8.1 is working fine and includes the updated package.json. Many thanks again.

[Philzen]

I've realized the Releases page (nor Tags) does not show 2.8.1 yet. In order to avoid confusion (and especially not have anybody accidentally trying to install the broken 2.8.0) i feel it may be vital to add it there.

Feeling a bit sorry for having caused all this late night kerfuffle on your side with this considerably non-critical fix – however on the upside this component won't cause any yarn install warnings anymore… and we've killed 50 % of the issues in this repo tonight 😆

[hiwllc]

ah yes, I just published the version on npm before the release in github, it's updated now 😊