Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(repo): use shell-emulator for better cross-platform compatibility #1743

Closed
wants to merge 2 commits into from

Conversation

danielbayley
Copy link

@danielbayley danielbayley commented Jun 30, 2024

Rollup Plugin Name: *

This PR contains:

  • bugfix
  • feature
  • refactor
  • documentation
  • other

Are tests included?

  • yes (bugfixes and features will not be merged without tests)
  • no

Breaking Changes?

  • yes (breaking changes will not be merged unless absolutely necessary)
  • no

If yes, then include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.

List any relevant issue numbers:

Description

I started work on a separate PR, but quickly ran into errors with the prepare scripts apparently not being cross-platform (if command not found—I am on macOS). Since this is a pnpm monorepo, and the scripts are very simple, why not make use of the shell-emulator .npmrc config option (which uses yarnpkg-shell)? This also means the dependency on del-cli is no longer necessary.

@tada5hi tada5hi changed the title fix(replace): use shell-emulator for better cross-platform compatibility chore(*): use shell-emulator for better cross-platform compatibility Jul 3, 2024
@tada5hi
Copy link
Member

tada5hi commented Jul 3, 2024

failing wasm test should be unrelated to pr?!
@shellscape

@shellscape shellscape changed the title chore(*): use shell-emulator for better cross-platform compatibility chore(repo): use shell-emulator for better cross-platform compatibility Sep 22, 2024
Copy link
Collaborator

@shellscape shellscape left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@danielbayley I'm good to merge this once the conflicts are resolved. To resolve the pnpm-lock conflict, run pnpm i in the repo root and pnpm will take care of it for us.

@danielbayley
Copy link
Author

@shellscape Should be resolved now…

@shellscape
Copy link
Collaborator

Closing as abandoned. Please feel free to reopen if you get back around to it.

@shellscape shellscape closed this Dec 15, 2024
@danielbayley
Copy link
Author

danielbayley commented Dec 15, 2024

Closing as abandoned. Please feel free to reopen if you get back around to it.

I resolved the issue, as requested @shellscape 🤷🏻‍♂️

My other PR (#1744) is on hold only because/if #1782 is set to supercede it…

But as already mentioned, this one should be good to go! @shellscape

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants