-
Notifications
You must be signed in to change notification settings - Fork 81
Audit and fix Next.js, Docusaurus, and Fastify build compatibility in monorepo #342
Copy link
Copy link
Closed
Labels
Third CampaignOfficial FWC26 campaign issue — eligible for campaign scoring and rewardsOfficial FWC26 campaign issue — eligible for campaign scoring and rewardsadvancedAdvanced difficulty tasks requiring significant domain knowledge and implementation effortAdvanced difficulty tasks requiring significant domain knowledge and implementation effortbuildBuild configuration, compilation, packaging, and build-system improvementsBuild configuration, compilation, packaging, and build-system improvementscompatibilityCompatibility improvements across environments, versions, platforms, or integrationsCompatibility improvements across environments, versions, platforms, or integrations
Description
Activity
Metadata
Metadata
Assignees
Labels
Third CampaignOfficial FWC26 campaign issue — eligible for campaign scoring and rewardsOfficial FWC26 campaign issue — eligible for campaign scoring and rewardsadvancedAdvanced difficulty tasks requiring significant domain knowledge and implementation effortAdvanced difficulty tasks requiring significant domain knowledge and implementation effortbuildBuild configuration, compilation, packaging, and build-system improvementsBuild configuration, compilation, packaging, and build-system improvementscompatibilityCompatibility improvements across environments, versions, platforms, or integrationsCompatibility improvements across environments, versions, platforms, or integrations
Background
The monorepo mixes three different build systems (Next.js 14, Docusaurus, Fastify) with incompatible or conflicting configurations. Recent build failures in
apps/dashboardand deprecation warnings inapps/docssuggest version mismatches, incompatible TypeScript settings, or misconfigured transpilation.Problem
apps/docsbuild logs show deprecated config options that will break in v4apps/access-apimay lack proper TypeScript and ESM supportExpected Outcome
Suggested Implementation
Audit versions in each app's
package.json:apps/docs: Docusaurus version, React versionapps/dashboard: Next.js version, React versionapps/access-api: Fastify version, Node.js versionapps/discord-bot: Discord.js versionCreate a spreadsheet or
VERSIONS.mddocumenting them.Fix Docusaurus deprecation in
apps/docs:docusaurus.config.jsto migratesiteConfig.onBrokenMarkdownLinkstositeConfig.markdown.hooks.onBrokenMarkdownLinks:onBrokenMarkdownLinksoption from the root levelUpdate Next.js configuration in
apps/dashboard:next.config.jstranspiles monorepo packages:typescript.tsconfigPathif neededConfigure Fastify TypeScript in
apps/access-api:tsconfig.jsontargets Node.js versionapps/access-api/README.mdCreate
VERSIONS.mdin the workspace root:Add GitHub Actions matrix for testing across Node versions:
Document in README.md:
Acceptance Criteria
apps/docsDocusaurus config updated to v3 standard (no warnings)apps/dashboardNext.js build succeeds with proper transpilationapps/access-apiFastify setup is documented and builds cleanlyVERSIONS.mddocuments all major dependencies and Node/pnpm versionsREADME.mdlinks toVERSIONS.mdfor setup requirementsAffected Files/Directories
apps/docs/docusaurus.config.jsapps/dashboard/next.config.jsapps/dashboard/tsconfig.jsonapps/access-api/tsconfig.jsonapps/access-api/README.mdVERSIONS.md(create).github/workflows/ci.yml(update with matrix)README.md(update)