Bernard

icon indicating a website link https://deepcode.io

icon company @ergodark, @nhscc, @uchicago-cs, @babel-utils, @projector-js icon location Somewhere, USA icon location Readme-Driven Developer, PR pusher, prolific package publisher, PhD'20 CS, loving maintainer of open source things, was there for the bad old days of JavaScript

Results 16 issues of Bernard

"Too many active WebGL contexts. Oldest context will be lost."

- [x] Your Hyper.app version is **3.2.3**. Please verify you're using the [latest](https://github.com/vercel/hyper/releases/latest) Hyper.app version - [x] I have searched the [issues](https://github.com/vercel/hyper/issues) of this repo and believe that this is...

conventional-changelog-conventionalcommits own unit tests fail when using [email protected]

1 comment

```bash git clone https://github.com/conventional-changelog/conventional-changelog cd conventional-changelog npm install cd packages/conventional-changelog-conventionalcommits npm run test-windows ``` All tests pass when using `[email protected]`. The following test fails mocha when upgrading the `conventional-changelog-core` dev-dependency...

Ensure outputUnreleased resolved correctly given lernaPackage/tagPrefix

As of `[email protected]`, [`options.outputUnreleased` is erroneously set to `true` when using a custom tag prefix via `tagPrefix` or `lernaPackage`](https://github.com/conventional-changelog/conventional-changelog/blob/conventional-changelog-core-v4.2.4/packages/conventional-changelog-core/lib/merge-config.js#L200-L211). This happens because [the check that determines `options.outputUnreleased`'s value is hardcoded...

Upgrade to API version 4?

2 comment

Hi. This is an excellent tool, thanks for this! Are there any plans to upgrade this to use the V4 version of the GitLab API? V3 has been deprecated as...

Add dummy EDITOR to env execa options (support for annotated tags?)

Closes #1708 Related to #1709, https://github.com/semantic-release/semantic-release/pull/1871

Transform tag to commit sha when getting notes

Closes #1708

fix(@types/node): use correct return types for performance.mark and performance.measure

9 comment

Please fill in this template. - [x] Use a meaningful title for the pull request. Include the name of the package modified. - [x] Test the change in your own...

Owner Approved
Critical package
The CI failed

fix(node-path): conform to NPM behavior when dealing with paths that include `path.delimiter`

Ref: #207 This makes NPX gracefully handle `path.delimiter` in a directory name similar to NPM in that they both "just work". I tried to make this PR "immediately" mergeable. Specifically,...

Conform to NPM behavior when dealing with paths that include `path.delimiter`

The problem is illustrated succinctly below: ![2018-09-14](https://user-images.githubusercontent.com/656017/45592363-1e235180-b930-11e8-899c-1a478df14a91.png) Essentially, both Linux and Windows allow for `path.delimiter` to appear in directory names. NPM handles this gracefully in all cases that I've encountered,...

Incorrect (duplicate) prerelease version determined even when git notes exist

13 comment

I'm using [GitHub Flow](https://guides.github.com/introduction/flow/)/[Trunk Based Development](https://trunkbaseddevelopment.com/) thanks to `semantic-release`, and it's great! I'm going to move all my packages over to a `semantic-release` CI/CD trunk-based flow, but most of them...