@toggl would be a great if you could just admit that the "new reports" were not a success (and are still unusable) and bring back the old reports for 2026?
This is the biggest issue with your new reports, put this back into the URL where it belongs and it will go a long way to making the new reports usable:
eslint v8 is deprecated, and I assume that it's going to be a long time until we can move to v9 due to incompatibilities, but other tools (eg tsc) are not going to stop delivering changes in the mean time. Is there a solution?
@dreioesterreich your website is completely broken. Most forms do not work and you don't provide any contact email addresses. Maybe you'd prefer your customers to go elsewhere?
I've been seeing a growing trend in big coorp online apps (usually Angular) adding a "noscroll" class to the body, blocking you from viewing anything below the fold. Why would they do this?
NEW: fetch-proxy
Build HTTP proxies with the JavaScript fetch API. Similar to node-http-proxy, but for fetch.
$ npm i @mjackson/fetch-proxy
https://t.co/D7BbrPL7Eq
I was just testing out Elixir 1.17’s new test breakpoints to verify that my test setup was actually doing what I thought 😅
Happy to report they’re 🤩
Just run your tests in `iex` with the `-b` flag! 👇
🔗 https://t.co/f0ERP5NAtt
#MyElixirStatus