Gregory Bolkenstijn comments

Results 11 comments of


                                            Gregory Bolkenstijn

Memory leaks

I'm having similar issues. Any word about progress on this?

Update NPM With Newest Version

+1 Example of getting the right version via the Git URL in `package.json`: ``` "dependencies": { "brainbrowser": "git://github.com/aces/brainbrowser.git#v2.5.5" } ```

Add new option to allow hex values to be output

> You're right it does need thinking about a little more. It's a shame sass-extract doesn't just return the colour in it's original form @andrewbrandwood I believe it does: https://github.com/jgranstrom/sass-extract#sasscolor

Next 12.2 newNextLinkBehavior support

@B2o5T Thanks, that fixed it for me!

[feat]: A way to define data in html

Request for support of oncuechange event on <track> elements

Can this be reopened?

Allow commenting to be turned off

I would love any of the above mentioned options! 🔥

Allow commenting to be turned off

@MorrisonCole Any chance this PR could be merged? https://github.com/MorrisonCole/pr-lint-action/pull/286

[All] Ensure all `document` handlers are attached to `ownerDocument`

We've run into this as well in our project. A solution or workaround would be greatly appreciated.

[eslint-patch] ESLint 9 - Failed to patch ESLint because the calling module was not recognized.

I'm encountering the same issue with ESLint 9.23.0 and `eslint-config-next`. The error occurs when trying to use `@rushstack/eslint-patch` with the new required flat config format. Package versions: - `eslint`: 9.23.0...