Skip to content

Exp: trying yarn@v4#2427

Closed
RobinTail wants to merge 19 commits intomasterfrom
try-yarn-latest
Closed

Exp: trying yarn@v4#2427
RobinTail wants to merge 19 commits intomasterfrom
try-yarn-latest

Conversation

@RobinTail
Copy link
Copy Markdown
Owner

@RobinTail RobinTail commented Feb 21, 2025

@RobinTail RobinTail added dependencies Pull requests that update a dependency file CI/CD labels Feb 21, 2025
@coveralls-official
Copy link
Copy Markdown

coveralls-official Bot commented Feb 21, 2025

Coverage Status

coverage: 100.0%. remained the same
when pulling f060372 on try-yarn-latest
into aa5cacc on master.

@RobinTail RobinTail added the miracle Mysterious events are happening here label Feb 21, 2025
@RobinTail
Copy link
Copy Markdown
Owner Author

  • The problem with yarn version having no way to configure --preid is significant.
  • yarn up is not good, though taze is ok
  • yarn publish still does not have --dry-run
    Should rather retry Exp: Trying pnpm #2067 which was cancelled due to the need of workspaces, that I do have now

@RobinTail RobinTail closed this Feb 21, 2025
@RobinTail RobinTail changed the title Using yarn@v4 Exp: trying yarn@v4 Feb 21, 2025
This was referenced Feb 21, 2025
@RobinTail
Copy link
Copy Markdown
Owner Author

wait a second... I've got an idea...

@RobinTail RobinTail reopened this Feb 26, 2025
@RobinTail
Copy link
Copy Markdown
Owner Author

RobinTail commented Feb 26, 2025

no, never mind

@RobinTail RobinTail closed this Feb 26, 2025
@RobinTail RobinTail mentioned this pull request Feb 26, 2025
RobinTail added a commit that referenced this pull request Jun 11, 2025
I see the need to migrate from `yarn` classic (despite my sincere love
of it) because I noticed warnings in Node 24 environment about the
deprecated methods used by `yarn`, that are (most likely) not going to
be fixed, so that `yarn` classic would probably become non-operational
in Node 25/26 (in a year).

Reiterating #2067 
Based on the findings of #2427 
And using the advantage of having workspaces introduced in #2374 

- it fixes `attw` issue in workspace
- `pnpm pack` does not work in workspace
  - pnpm/pnpm#4351
  - using `working-directory` in CI
- `pnpm version` does not work in workspace, but there is a workaround
pnpm/pnpm#8064
- but it does not work due to another `npm` bug:
npm/cli#2010
  - possible solution https://www.npmjs.com/package/bumpp
- but overall clarity and consistency is much better than even `yarn@v4`
that I tried recently

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Summary by CodeRabbit

- **Chores**
- Migrated project tooling and workflows from Yarn to pnpm for package
management.
  - Updated all CI workflows and pre-commit hooks to use pnpm commands.
- Adjusted documentation and contributing guidelines to reflect pnpm
usage.
- Introduced a pnpm workspace configuration and updated ignore files
accordingly.
- Updated package.json scripts and resolutions to align with pnpm usage.
- Added explicit workspace dependencies in test and example projects for
improved clarity and reliability.

- **Bug Fixes**
- Improved TypeScript compatibility with a workaround for a specific
type error.

- **Refactor**
- Simplified internal scripts and utility logic by removing Ramda
dependencies and adopting native JavaScript approaches.

- **Style**
- Updated package scripts and configuration files for consistency with
pnpm standards.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD dependencies Pull requests that update a dependency file miracle Mysterious events are happening here

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant