Mike McCready

icon location Munich, Germany

Results 2194 comments of Mike McCready

[Feature] Alternative to Node.js experimental corepack to manage package manager version

I would like to be able to recommend Yarn (Modern) with good conscience for production use as a migration path from Yarn v1 Classic. This is the situation I see:...

docs: The url to the yarn corepack documentation is not found (invalid url) when corepack is enabled for the repo, but not the action.

@jpbnetley If you run the following ```shell cd $(mktemp -d) corepack enable yarn corepack use yarn corepack disable yarn npm install [email protected] -g yarn cache dir ``` in a local...

docs: The url to the yarn corepack documentation is not found (invalid url) when corepack is enabled for the repo, but not the action.

@jpbnetley You've probably solved this by now, but in case anybody else is reading this: In order to fix the workflow you will need to add: ```shell - run: corepack...

docs: The url to the yarn corepack documentation is not found (invalid url) when corepack is enabled for the repo, but not the action.

@jpbnetley I looked at the URL in the error message in https://github.com/yarnpkg/yarn/issues/9182#issuecomment-2692668651 and I made a suggestion to improve it. It's possible that the maintainers may be reading this and...

docs: The url to the yarn corepack documentation is not found (invalid url) when corepack is enabled for the repo, but not the action.

@laguta-danil > "It turns out that once you activate Corepack, there's no way to revert it? Except for explicitly setting the packageManager version in the package.json? Otherwise, it always gives...

docs: The url to the yarn corepack documentation is not found (invalid url) when corepack is enabled for the repo, but not the action.

@luzpaz > soft bump I would be pleasantly surprised if there is any response from the Yarn team, since it already says on the main page of this repo: ![Image](https://github.com/user-attachments/assets/c6f2d6ed-de81-4448-9c7d-ca9901a9cc9b)...

breaking: 14.0.0 Release

- When the `release/14.0.0` branch is rebased on `develop` I'll submit https://github.com/cypress-io/cypress/pull/30671 to [CONTRIBUTING > Requirements](https://github.com/cypress-io/cypress/blob/develop/CONTRIBUTING.md#requirements) as a follow-on to PR #30633

Support ESLint v9

In the meantime it may be a good idea to add a note to the [README](https://github.com/bmish/eslint-doc-generator/blob/main/README.md) concerning the status with ESLint `v9`. Currently there is no restriction for ESLint `v9`...

Support ESLint v9

@bmish Hello again 😄 Same confirmation steps as before, running under Windows 11, except updated to ESLint `9.2.0`. ```text git clone https://github.com/cypress-io/eslint-plugin-cypress cd eslint-plugin-cypress npm ci npm install eslint@9 [email protected]...

Support ESLint v9

@bmish Are you going to pick this up some time? I see that https://typescript-eslint.io/blog/announcing-typescript-eslint-v8 brings in ESLint v9 support and that was one of the blockers.