ylemkimon

Please report the issue in https://github.com/KaTeX/KaTeX/security/advisories/GHSA-cvr6-37gx-v8wc.

With the current setup, screenshots should be manually tested (CIs run with the old version).

Similar to https://github.com/dependabot/dependabot-core/issues/1297#issuecomment-621458459, I'm using a GitHub Actions workflow to fix and update PRs created by Dependabot. This way we can still benefit from its version update logic and release...

If there are no dependencies in the ESM, there should be no difference from the original jsDelivr URLs except minification, right? For instance, are https://cdn.jsdelivr.net/npm/[email protected]/dist/katex.mjs (there is no import statement)...

RFC 2606 states and reserves: > The ".localhost" TLD has traditionally been statically defined in host DNS implementations as having an A record pointing to the loop back IP address...

> Maybe we can use docker to run test, better than local puppeteer to run I've used Selenium in other projects and had a not bad experience. Its error rate...

`react-error-overlay` seems to be easily integrable, adding it to the client works out of the box. Two notes: - it doesn't support build warnings, i.e., build errors are not dismissable...

@sibelius If you're using dev server v4, you should put `overlay` in `client` (https://github.com/webpack/webpack-dev-server/blob/master/migration-v4.md): ```js devServer: { client: { overlay: { warnings: false, errors: true } } } ```

@TrySound I wonder how Babel solved the peer dependency problem when moving from Babel 6 to 7.

@TrySound I remember there were lots of packages declaring unscoped Babel packages, e.g. `babel-core`, as peer dependency. I'm curious how they moved to using scoped Babel packages (`@babel/core`) as peer...