Migrate from pnpm/turborepo to bun package manager

Co-authored-by: r-near <[email protected]>

Author: Copilot

.github/pull_request_template.md

@@ -9,7 +9,7 @@ Happy contributing!
 - [ ] I have read the [Contributing Guidelines on pull requests](https://github.com/near/near-api-js/blob/master/CONTRIBUTING.md).
 - [ ] Commit messages follow the [conventional commits](https://www.conventionalcommits.org/) spec
 - [ ] **If this is a code change**: I have written unit tests.
-- [ ] **If this changes code in a published package**: I have run `pnpm changeset` to create a `changeset` JSON document appropriate for this change.
+- [ ] **If this changes code in a published package**: I have run `bun changeset` to create a `changeset` JSON document appropriate for this change.
 - [ ] **If this is a new API or substantial change**: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.
 
 ## Motivation

.github/workflows/pull-request.yml

@@ -21,46 +21,36 @@ jobs:
     - name: Checkout repository
       uses: actions/checkout@v4
 
-
-    - name: Cache turbo build setup
-      uses: actions/cache@v4
-      with: 
-        path: .turbo
-        key: ${{ runner.os }}-turbo-${{ github.sha }}
-        restore-keys: |
-          ${{ runner.os }}-turbo-
-
-    - name: Setup pnpm
-      uses: pnpm/action-setup@v4
+    - name: Setup bun
+      uses: oven-sh/setup-bun@v2
       with:
-        version: 10.4.1
+        bun-version: 1.1.42
 
     - name: Setup Node
       uses: actions/setup-node@v4
       with:
         node-version: 20.18.3
-        cache: pnpm
 
     - name: Install dependencies
-      run: pnpm install
+      run: bun install
 
     - name: Typecheck
-      run: pnpm typecheck
+      run: bun run typecheck
 
     - name: Build
-      run: pnpm build
+      run: bun run build
 
     - name: Lint
-      run: pnpm lint
+      run: bun run lint
 
     - name: Unit tests
-      run: pnpm test
+      run: bun run test
 
     - name: Check exports
-      run: pnpm check-exports
+      run: bun run check-exports
 
     - name: E2E tests
-      run: pnpm it --ignore-workspace --dir e2e
+      run: cd e2e && bun install && bun run test
 
   changeset-checks:
     runs-on: ubuntu-latest
@@ -88,7 +78,7 @@ jobs:
       if: steps.source-files.outputs.has_changed == 'true' && steps.changesets.outputs.has_added == 'false'
       run: |
           echo "❌ Source files changed, but no new changset file was added."
-          echo "Please run 'pnpm changeset' and commit the generated file."
+          echo "Please run 'bun changeset' and commit the generated file."
           exit 1
     
     - name: Fail if changeset was added, but no source files were changed

.github/workflows/release.yml

@@ -21,27 +21,26 @@ jobs:
       - name: Checkout Repo
         uses: actions/checkout@v4
 
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
+      - name: Setup bun
+        uses: oven-sh/setup-bun@v2
         with:
-          version: 10.4.1
+          bun-version: 1.1.42
 
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
           node-version: 20.18.3
-          cache: pnpm
 
       - name: Install Dependencies
-        run: pnpm install
+        run: bun install
 
       - name: Build Packages
-        run: pnpm build
+        run: bun run build
 
       - name: Create Release Pull Request or Publish to NPM
         uses: changesets/action@v1
         with:
-          publish: pnpm release
+          publish: bun run release
           commit: "chore(release): publish packages"
           title: "Publish packages"
           createGithubReleases: ${{ github.ref_name == 'master' }}

.github/workflows/typedoc-generator.yml

@@ -9,7 +9,6 @@ env:
   NODE_VERSION: 20.18.3
   ENTRY_FILE: 'packages'
   CONFIG_PATH: 'tsconfig.base.json'
-  USES_PNPM: 'true'
   DESTINATION_FOLDER: "docs"
 
 jobs:
@@ -21,24 +20,23 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
+      - name: Setup bun
+        uses: oven-sh/setup-bun@v2
         with:
-          version: 10.4.1
+          bun-version: 1.1.42
 
       - uses: actions/setup-node@v4
         with:
           node-version: ${{ env.NODE_VERSION }}
-          cache: 'pnpm'
 
       - name: Install dependencies
-        run: pnpm install
+        run: bun install
 
       - name: Build project
-        run:  pnpm build
+        run:  bun run build
 
       - name: Build documentation
-        run:  pnpm docs:generate
+        run:  bun run docs:generate
 
       - name: Deploy to GitHub pages
         uses: JamesIves/github-pages-deploy-action@v4

.gitignore

@@ -22,6 +22,4 @@ lib/
 # Generated test files
 test-keys/
 
-.turbo
-
 typedoc-docs/

.husky/commit-msg

@@ -1,3 +1,3 @@
 #!/bin/sh
 
-pnpm commitlint --edit $1
+bun commitlint --edit $1

.husky/pre-push

@@ -1,3 +1,3 @@
 #!/bin/sh
 
-pnpm lint
+bun lint

README.md

@@ -19,23 +19,23 @@ NEAR JavaScript API is a complete library to interact with the NEAR blockchain.
 
 1. Install dependencies
 
-       pnpm install
+       bun install
 
 2. Run continuous build with:
 
-       pnpm -r compile -w
+       bun run compile -w
 
 ### Publish
 
 Prepare `dist` version by running:
 
-    pnpm dist
+    bun run dist
 
 ### Integration Test
 
 Start the node by following instructions from [nearcore](https://github.com/nearprotocol/nearcore), then
 
-    pnpm test
+    bun run test
 
 Tests use sample contract from `near-hello` npm package, see https://github.com/nearprotocol/near-hello
 
@@ -45,21 +45,18 @@ From the root directory, run the following commands:
 
 ```
 cd e2e
-pnpm install --ignore-workspace
-pnpm test
+bun install
+bun run test
 ```
 
-The `--ignore-workspace` flag is required because the `e2e` project is intentionally excluded from the workspace.
-This setup ensures that packages are installed just like a real application would — as standalone builds. Workspace linking would not allow this, as it forces symlinks instead of proper package installations.
-
 ### Update error schema
 
 Follow next steps:
 
 1. [Optionally, set a specific hash for the commit with errors in the nearcore](https://github.com/near/near-api-js/blob/master/packages/utils/fetch_error_schema.js#L4-L5)
 2. Fetch new schema: `node fetch_error_schema.js`
-3. `pnpm build` and `pnpm test` to check tests still work
-4. `pnpm changeset` to generate a changeset with a minor bump for the @near-js/utils package
+3. `bun run build` and `bun run test` to check tests still work
+4. `bun changeset` to generate a changeset with a minor bump for the @near-js/utils package
 5. commit all changes and submit a PR on GitHub
 
 ## Packages

README2.md

@@ -9,7 +9,7 @@ npm install near-api-js
 # or
 yarn add near-api-js
 # or
-pnpm add near-api-js
+bun add near-api-js
 ```
 
 ## Why near-api-js?

TOOLING.md

@@ -2,11 +2,8 @@
 
 This document describes at a high level some the key tools used across `near-js`.
 
-## Package Manager - [PNPM](https://pnpm.io/)
-PNPM is a package manager focused on fast installations while still being disk efficient. It manages dependency installations across the monorepo as well as linking interdependent packages. Unlike other package managers, PNPM creates a non-flat `node_modules` structure which ensures packages only have access to dependencies defined in their `package.json`.
-
-## Build System - [Turborepo](https://turborepo.org/)
-Turborepo provides tooling for orchestrating commands across the monorepo. Similar to Yarn Workspaces, Turborepo can run tasks within each project via a single command, but rather than executing serially, Turborepo has various performance enhancing features such as task parallelization and local/remote caching.
+## Package Manager - [Bun](https://bun.sh/)
+Bun is a fast all-in-one JavaScript runtime and toolkit with a built-in bundler, test runner, and Node.js-compatible package manager. It provides significantly faster package installations compared to npm, yarn, or pnpm while maintaining full compatibility with the npm ecosystem.
 
 ## Package Publishing - [Changesets](https://github.com/changesets/changesets)
 Changesets manages package versioning, changelog generation, and publishing to the package registry. Changesets provides a CLI to simplify bumping packages and adding changelog entries, it then automates versioning and publishing via GitHub Actions.