--log-output currently supports only none (disabled), stdout, stderr and loki.
Supporting local files should be simple and will be beneficial for debugging, or in CI environments, and it can also be used by log-forwarding tools to ship the logs pretty much anywhere. Combined
DNS preanalyze is a way to reduce DNS analyze time:
<meta http-equiv="x-dns-prefetch-control" content="on" />
<link rel="dns-prefetch" href="http://www.baidu.com" />
The Storybook API has changed quite a lot since Solid's Storybook docs were written in 2019. It would be really helpful (and I think go a loooong way toward helping drive adoption, long-term) if Solid could:
Describe the bug
The markup version of the readme that is displayed in the main page for this repo contains the following links:
Status code [404:NotFound] - Link: https://keyword-2-ecd7b.firebaseapp.com/
Status code [404:NotFound] - Link: https://github.com/GoogleChromeLabs/quicklink/blob/master/#custom-ignore-patterns
(The links in the readme’s markdown may appear different to the link
I currently have a very big hook, with dozens of useStates, lots of them have empty arrays which trigger unncesary re-renders. But I don't know which is the one doing it each time wdyr logs it's output. I get:
Re-rendered because of hook changes:
[hook useState result]
...diff
When would be very useful for me is:
Re-rendered because of hook changes:
[hook useState result]
Various characters (e.g. |) if used in a Params will end up invalidating the generated markdown, causing it to render incorrectly. It'd be helpful if benchmarkdotnet could escape the markdown output, e.g. output \| instead of |.
Running validator https://validator.w3.org on basic <picture> elements as per setup config should not result in errors.
Currently when running validator on:
<picture class="lozad" style="display: block; min-height: 1rem" data-iesrc="images/thumbs/04.jpg" data-alt="">
<source srcset="images/thumbs/04.jpg" media="(min-width: 1280px)">
it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.
now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.
a lot of code can already be regression-tested by simply running all the demos and val
There's a lot of place for improvement of the documentation.
ngx-build-plusThe content of the documentation is in the GitHub page [repo](https://github.com/guess-js/guess-
Describe the bug
The "ES2015 exports introduced. Not side-effect free yet, hence limited tree-shake ability." Tooltip in the Size-per-package-Version graph is displayed behind the graphs bars, possibly making the tooltip text unreadable.
To Reproduce
Found on this page:
Is your feature request related to a problem? Please describe.
Many static type checkers have issues finding Cython's stubs.
Here is from running mypy on my current project:
error: Skipping analyzing "cython": found module but no type hints or library stubs
The same issue can be seen when using import Cython as cython:
error: Skipping analyzing "Cython": found module but
Add a description, image, and links to the performance topic page so that developers can more easily learn about it.
To associate your repository with the performance topic, visit your repo's landing page and select "manage topics."
I think you should remove all the non-technical relevant stuff and instead of the strong attribution, simply replace it with "Based on the article ... by Eran Hammer". I'm giving you full permission to use this text as you find useful. Don't be shy to change it.
Originally posted by @hueniverse in fastify/fastify#3609 (comment)