update pnpm-link.sh

Author: pkieltyka

README.md

@@ -39,29 +39,29 @@ or
 Below are notes and instructions on how to get your development environment up and running,
 and enjoyable.
 
-1. **Install dependencies** -- we use yarn workspaces, so please use yarn instead of npm.
-   Run, `yarn install`
+1. **Install dependencies**
+   Run, `pnpm install`
 
 2. **Workflow** -- we use the amazing [preconstruct](https://github.com/preconstruct/preconstruct)
    package to handle our monorepo build system.
 
 3. **Local dev** -- when you're working on the code in this repository, you can safely run
-   `yarn dev` at the root-level, which will link all packages/** together, so that when a
+   `pnpm dev` at the root-level, which will link all packages/** together, so that when a
    local dependency from packages/** is used by another, it will automatically be linked
-   without having to run a build command. Just remember: run `yarn dev` anytime you developing
-   in this repo. Note, that when you run `yarn build` it will clear the dev environment, so
-   you will need to run `yarn dev` again after a build. However, `yarn build` should only be
+   without having to run a build command. Just remember: run `pnpm dev` anytime you developing
+   in this repo. Note, that when you run `pnpm build` it will clear the dev environment, so
+   you will need to run `pnpm dev` again after a build. However, `pnpm build` should only be
    used when making a release.
 
-4. **Testing** -- to test the system, you can run `yarn test` at the top-level or at an individual
+4. **Testing** -- to test the system, you can run `pnpm test` at the top-level or at an individual
    package-level.
 
-5. **Type-checking** -- to typecheck the system you can run `yarn typecheck` at any level.
+5. **Type-checking** -- to typecheck the system you can run `pnpm typecheck` at any level.
 
-6. **Building** -- to _compile_ the project to dist files for a release, run `yarn build` at
+6. **Building** -- to _compile_ the project to dist files for a release, run `pnpm build` at
    the root-level. Note building packages repeatedly during development is unnecessary with
-   `preconstruct`. During local development run `yarn dev` and when building to make a release,
-   run `yarn build`.
+   `preconstruct`. During local development run `pnpm dev` and when building to make a release,
+   run `pnpm build`.
 
 7. **Versioning** -- this repository uses the handy [changesets](https://github.com/atlassian/changesets)
    package for package versioning across the monorepo, as well as changelogs. See _Releasing_ section below.
@@ -73,17 +73,17 @@ and enjoyable.
 
 ### How to do a release
 
-1. Run `yarn` to make sure everything is up to date
+1. Run `pnpm` to make sure everything is up to date
 2. Code.. do your magic
-3. Run `yarn changeset` to generate a new .changeset/ entry explaining the code changes
+3. Run `pnpm changeset` to generate a new .changeset/ entry explaining the code changes
 4. Version bump all packages regardless of them having changes or not
 5. Commit and submit your changes as a PR for review
 6. Once merged and you're ready to make a release, continue to the next step. If you're not
    ready to make a release, then go back to step 2.
-7. Run `yarn build && yarn test` to double check all tests pass
-8. Run `yarn version-packages` to bump versions of the packages
+7. Run `pnpm build && pnpm test` to double check all tests pass
+8. Run `pnpm version-packages` to bump versions of the packages
 9. Commit files after versioning. This is the commit that will be published and tagged: `git push --no-verify`
-10. Run `yarn release`. If the 2FA code timesout while publishing, run the command again
+10. Run `pnpm release`. If the 2FA code timesout while publishing, run the command again
     with a new code, only the packages that were not published will be published.
 11. Finally, push your git tags, via: `git push --tags --no-verify`
 
@@ -92,15 +92,15 @@ and enjoyable.
 
 NOTE: snapshot release is for dev preview, it's similar to the above, but:
 
-1. `yarn changeset`
-2. `yarn changeset version --snapshot`
-3. `yarn changeset publish --tag snapshot`
+1. `pnpm changeset`
+2. `pnpm changeset version --snapshot`
+3. `pnpm changeset publish --tag snapshot`
 
 
 ## NOTES
 
-1. Browser tests can be run with `yarn test` or, separately `yarn test:server` and `yarn test:run`
-2. To run a specific test, run `yarn test:only <test-file-basename>`, ie. `yarn test:only window-transport`
+1. Browser tests can be run with `pnpm test` or, separately `pnpm test:server` and `pnpm test:run`
+2. To run a specific test, run `pnpm test:only <test-file-basename>`, ie. `pnpm test:only window-transport`
 
 
 ## TIPS

packages/0xsequence/README.md

@@ -20,11 +20,11 @@ Sequence is a critical piece of software and any change should be delivered via
 workflow. 
 
 As well, sequence.js's monorepo tooling is setup with preconstruct, which links all sub-packages together
-so it feels like a single program and is easy to work with. Please run `yarn dev` in the root of `sequence.js/`
+so it feels like a single program and is easy to work with. Please run `pnpm dev` in the root of `sequence.js/`
 folder to ensure the monorepo is in 'dev-mode'.
 
-Second, you can run the test suite directly from console with a single `yarn test`, or you can boot up the Typescript
-compiling server (`yarn test:server`) and ethereum test node (`yarn start:hardhat` and `yarn start:hardhat2`) manually
+Second, you can run the test suite directly from console with a single `pnpm test`, or you can boot up the Typescript
+compiling server (`pnpm test:server`) and ethereum test node (`pnpm start:hardhat` and `pnpm start:hardhat2`) manually
 in separate terminals, and then run a specific test directly from your browser instance. We recommend running the
 test stack separately and running specific browser tests manually during development. See [here for recommended setup](./#from-browser).
 
@@ -40,9 +40,9 @@ we highly recommend to view your tests running from the browser as its more clea
 
 ### From Browser
 
-1. `yarn test:server` -- in one terminal, to start the webpack server compiling typescript
-2. `yarn start:hardhat` -- in a second terminal, to start hardhat local ethereum test node
-3. `yarn start:hardhat2` -- (2nd chain) in a third terminal, to start hardhat2 local ethereum test node
+1. `pnpm test:server` -- in one terminal, to start the webpack server compiling typescript
+2. `pnpm start:hardhat` -- in a second terminal, to start hardhat local ethereum test node
+3. `pnpm start:hardhat2` -- (2nd chain) in a third terminal, to start hardhat2 local ethereum test node
 4. open browser to `http://localhost:9999/{browser-test-dir}/{test-filename}.test.html` for example,
    http://localhost:9999/wallet-provider/dapp.test.html
 5. open your browser console so you can see the tests running and their results.
@@ -53,14 +53,14 @@ following the last test case, so you will preempt the runner after a certain tes
 As well, since you have all the services running in terminals, you can also execute commands via
 the cli by calling `test:run`, which is similar to step 4 above, but executing all tests from the terminal.
 There is also the `test:only` command if you'd like to execute a specific test from ./tests/browser/*.spec.ts
-file, ie. `yarn test:only window-transport`.
+file, ie. `pnpm test:only window-transport`.
 
 
 ### From CLI
 
 With a single command, you can spin up the testing stack and execute tests:
 
-`yarn test`
+`pnpm test`
 
 This is useful for a sanity check to ensure tests pass, or using it with the CI. However, if you're
 developing on sequence.js, its highly recommended you follow the [development workflow instructions](./#development-workflow).

scripts/yarn-link.sh scripts/pnpm-link.sh

@@ -23,10 +23,14 @@ case "$option" in
     ;;
 esac
 
-packages=(./packages/*)
+repo_dir=$(cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && cd .. && pwd)
+
+packages=($repo_dir/packages/*)
 for p in "${packages[@]}"
 do
-  (cd $p && yarn $option)
+  x=$(realpath $p)
+  # echo $x
+  pnpm link $x
 done
 
 exit $?