Skip to content

Fix Turbo v2 setup issues when following official Midnight Network tutorial#1002

Open
ShawnTseng wants to merge 14 commits into
midnightntwrk:mainfrom
ShawnTseng:main
Open

Fix Turbo v2 setup issues when following official Midnight Network tutorial#1002
ShawnTseng wants to merge 14 commits into
midnightntwrk:mainfrom
ShawnTseng:main

Conversation

@ShawnTseng

@ShawnTseng ShawnTseng commented Aug 24, 2025

Copy link
Copy Markdown

While following the official Midnight Network tutorial for building the example-bboard DApp (https://docs.midnight.network/develop/tutorial/creating/bboard-dapp#compiling-and-running-the-dapp), several issues prevented npx turbo build from running correctly.

This PR fixes those issues:

  • Missing packageManager field: Added to root package.json as required by Turbo v2.
  • turbo.json location: Moved to the repository root to comply with Turbo v2 expectations.
  • Deprecated outputMode: Replaced with outputLogs in turbo.json.
  • pipeline field: Renamed to tasks in turbo.json for Turbo v2.
  • dependsOn syntax: Updated to correctly reference compact tasks.
  • Turbo cache: Added .turbo to .gitignore.
  • Standalone script: Runs locally using ts-node/esm on the original .ts files, after pulling required Docker images.

These fixes make the build scripts run successfully while following the tutorial instructions.

@ShawnTseng ShawnTseng requested a review from a team as a code owner August 24, 2025 14:06
@CLAassistant

CLAassistant commented Aug 24, 2025

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ gilescope
❌ ShawnTseng
You have signed the CLA already but the status is still pending? Let us recheck it.

Comment thread package.json Outdated
- Added "engines" field to enforce Node version >=20
- Standalone script remains using ts-node/esm with experimental specifier resolution
Add dangerouslyDisablePackageManagerCheck flag to resolve build failures
when running npx turbo build. This allows flexibility in package manager
usage without requiring a specific npm version in packageManager field.

ref: https://turborepo.com/docs/reference/configuration#dangerouslydisablepackagemanagercheck

@bytrangle bytrangle left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Look neat to me. There are some changes in Turbo that are not documented unless you dig deep into their blog. These changes look neat to me.

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.

6 participants