You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Error: Could not resolve module "node:module" in jiti after upgrading to Tailwind v4 in Plasmo #1188
After upgrading to Tailwind v4 using npx @tailwindcss/upgrade@next, the Plasmo build fails with the following error:
🔴 ERROR | Build failed. To debug, run plasmo dev --verbose.
🔴 ERROR | Could not resolve module "node:module" from "/Users/guilhermomasid/Documents/trash/plasmo-tailwind/node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/lib/jiti.cjs"
Steps to Reproduce
Create a new Plasmo extension with TailwindCSS using:
The main branch contains the unmodified Plasmo Tailwind example.
The feat/tailwind-v4 branch contains the project after the Tailwind v4 upgrade.
A pull request comparing the changes is available here: PR #1.
Expected Behavior
The project should build successfully after upgrading to Tailwind v4.
Actual Behavior
The build fails with a module resolution error related to jiti@2.4.2.
Environment
TailwindCSS v4
Jiti v2.4.2
Node.js version: v22.13.1
Package manager: pnpm
Additional Notes
This issue seems related to jiti@2.4.2 and its inability to resolve the node:module package. Any insights or workarounds would be greatly appreciated.
Version
Latest
What OS are you seeing the problem on?
MacOSX
What browsers are you seeing the problem on?
Chrome
Relevant log output
p dev
> plasmo-tailwind@0.0.1 dev /Users/guilhermomasid/Documents/trash/plasmo-tailwind
> plasmo dev
🟣 Plasmo v0.90.2
🔴 The Browser Extension Framework
🔵 INFO | Starting the extension development server...
🔵 INFO | Building for target: chrome-mv3
🔵 INFO | Loaded environment variables from: []
(node:59554) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
🔴 ERROR | Build failed. To debug, run plasmo dev --verbose.
🔴 ERROR | Could not resolve module "node:module" from "/Users/guilhermomasid/Documents/trash/plasmo-tailwind/node\_modules/.pnpm/jiti@2.4.2/node\_modules/jiti/lib/jiti.cjs"
+1 on this, got a monorepo setup with 4 apps using the same shared design system with tailwind v4, have to make the PR wait until this gets resolved otherwise our extension will break.
@ctrhub The issue here is specifically related to upgrading Tailwind to version 4. The code you provided is using Tailwind version 3, which currently works fine with Plasmo.
Reacted by ctrhub, Anubis, Ammar Elbehery, Benjamín Vicente, Obinna Akahara, Ethan Lerner, situ2001, Truong Nguyen, zltl, Albérico Dias Barreto Filho and 9 more
So I found a hacky way around it. You can go into your node_modules folder and look for the file at ...node\_modules/@tailwindcss/node/node\_modules/jiti/dist/jiti.cjs
You want to manually remove the node:... prefix. You'll need to do this about a dozen more times throughout the node package.
This is a naming convention in recent node versions. I'm working to find a more permanent/reasonable solution (probably involving an alias is my guess)
Got the answer. You have to patch the package (for now)
In my case, I use bun.sh, so:
bun patch jiti@2.4.2
but with npm, it would be
npm install --save-dev patch-package postinstall-postinstall
# After manually making your change to node_modules
npx patch-package @tailwindcss/node
And then you want to manually go into your node modules and perform the steps above: find the references to "node:modules" that are mentioned in the error message and replace it with "modules".
You'll need to do it for some other "node:... references as well. Just follow the plasmo console error message.
Hopefully we get a better fix soon.
Reacted by Morgän, Ethan Lerner, situ2001, Tina Holly, Giorgio Bertolotti, Zi Yang, Connor Hansen and Leon Fedotov
Got the answer. You have to patch the package (for now)
In my case, I use bun.sh, so:
bun patch jiti@2.4.2
but with npm, it would be
npm install --save-dev patch-package postinstall-postinstall
# After manually making your change to node_modules
npx patch-package @tailwindcss/node
And then you want to manually go into your node modules and perform the steps above: find the references to "node:modules" that are mentioned in the error message and replace it with "modules".
You'll need to do it for some other "node:... references as well. Just follow the plasmo console error message.
Hopefully we get a better fix soon.
I can't find the file you're talking about. Can you explain some more?
🔴 ERROR | Build failed. To debug, run plasmo dev --verbose.
🔴 ERROR | Could not resolve module "node:module" from "/Users/guilhermomasid/Documents/trash/plasmo-tailwind/node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/lib/jiti.cjs"
You want to go to the file at this path (replace it with your own path)
/Users/ ...<your own path>... /node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/lib/jiti.cjs
And then you want to search for "node:modules" inside the file, and replace it with "modules"
You will need to repeat this with other similar import like "node:os" "node:fs" "node:..."
Make sure your plasmo dev server keeps running when you do this. The error message will tell you what file needs to be changed next. Once you've changed all the references, then your extension should build!
After that, then you can follow the instructions above to patch you package.json
Hope this helps!
Got the answer. You have to patch the package (for now)
In my case, I use bun.sh, so:
bun patch jiti@2.4.2
but with npm, it would be
npm install --save-dev patch-package postinstall-postinstall
# After manually making your change to node_modules
npx patch-package @tailwindcss/node
And then you want to manually go into your node modules and perform the steps above: find the references to "node:modules" that are mentioned in the error message and replace it with "modules".
You'll need to do it for some other "node:... references as well. Just follow the plasmo console error message.
🔴 ERROR | Build failed. To debug, run plasmo dev --verbose.
🔴 ERROR | Could not resolve module "node:module" from "/Users/guilhermomasid/Documents/trash/plasmo-tailwind/node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/lib/jiti.cjs"
You want to go to the file at this path (replace it with your own path)
/Users/ ...<your own path>... /node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/lib/jiti.cjs
And then you want to search for "node:modules" inside the file, and replace it with "modules"
You will need to repeat this with other similar import like "node:os""node:fs""node:..."
Make sure your plasmo dev server keeps running when you do this. The error message will tell you what file needs to be changed next. Once you've changed all the references, then your extension should build!
After that, then you can follow the instructions above to patch you package.json
Hope this helps!
Got the answer. You have to patch the package (for now)
In my case, I use bun.sh, so: bun patch jiti@2.4.2
but with npm, it would be
npm install --save-dev patch-package postinstall-postinstall
# After manually making your change to node_modules
npx patch-package @tailwindcss/node
And then you want to manually go into your node modules and perform the steps above: find the references to "node:modules" that are mentioned in the error message and replace it with "modules".
You'll need to do it for some other "node:... references as well. Just follow the plasmo console error message.
Hopefully we get a better fix soon.
Thank you!
Can you share one of the edits?
I tried I still get an error in the file.
🔴 ERROR | Build failed. To debug, run plasmo dev --verbose.
🔴 ERROR | Could not resolve module "modules" from "*/node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/lib/jiti.cjs"
Got the answer. You have to patch the package (for now)
In my case, I use bun.sh, so:
bun patch jiti@2.4.2
but with npm, it would be
npm install --save-dev patch-package postinstall-postinstall
# After manually making your change to node_modules
npx patch-package @tailwindcss/node
And then you want to manually go into your node modules and perform the steps above: find the references to "node:modules" that are mentioned in the error message and replace it with "modules".
You'll need to do it for some other "node:... references as well. Just follow the plasmo console error message.
Hopefully we get a better fix soon.
Thanks @ObinnaAka for this! I am using pnpm and did the following:
Ran pnpm patch jiti@2.4.2.
In the patch code that pnpm created for me at node_modules/.pnpm_patches/jiti@2.4.2, I did a find and replace, finding all "node: and replacing with " (so as to remove the node: as suggested).
Committed the patch with pnpm patch-commit node_modules/.pnpm_patches/jiti@2.4.2.
Works great, thanks! I appreciate you taking the time to share your fix.
Based on the comments I ended up writing a script that would patch the files everytime after install. Also helpful if you are sharing code with a team and they need to do the same patch.
scripts/patch.js:
#!/usr/bin/env node
/** * Plasmo + Tailwind v4 Compatibility Patch * * Automatically fixes "node:" import issues in jiti and @tailwindcss/oxide * that cause Plasmo builds to fail when using Tailwind CSS v4. * * @see https://github.com/PlasmoHQ/plasmo/issues/1188 */constfs=require('fs');constpath=require('path');// Console colorsconstc={reset: '\x1b[0m',red: '\x1b[31m',green: '\x1b[32m',yellow: '\x1b[33m',blue: '\x1b[34m',cyan: '\x1b[36m'};constlog=(msg,color='reset')=>console.log(`${c[color]}${msg}${c.reset}`);/** * Find package files that need patching */constfindPackageFiles=()=>{constnodeModules=path.resolve('node_modules');if(!fs.existsSync(nodeModules))return[];constfiles=[];constpnpmPath=path.join(nodeModules,'.pnpm');// Helper to safely read directoryconstreadDir=(dir)=>{try{returnfs.existsSync(dir) ? fs.readdirSync(dir) : [];}catch{return[];}};// Helper to check file existsconstfileExists=(filePath)=>{try{returnfs.existsSync(filePath);}catch{returnfalse;}};// Find jiti filesconstfindJitiFiles=(basePath)=>{constjitiPath=path.join(basePath,'jiti');if(!fileExists(jitiPath))return[];consttargets=['dist/jiti.cjs','dist/babel.cjs','lib/jiti.cjs'];returntargets.map(target=>path.join(jitiPath,target)).filter(fileExists);};// Find oxide filesconstfindOxideFiles=(basePath)=>{constoxidePath=path.join(basePath,'@tailwindcss','oxide','index.js');returnfileExists(oxidePath) ? [oxidePath] : [];};// Search pnpm structureif(fileExists(pnpmPath)){readDir(pnpmPath).forEach(entry=>{if(entry.startsWith('jiti@')){constpackagePath=path.join(pnpmPath,entry,'node_modules');files.push(...findJitiFiles(packagePath));}if(entry.startsWith('@tailwindcss+oxide@')||entry.startsWith('%40tailwindcss+oxide@')){constpackagePath=path.join(pnpmPath,entry,'node_modules');files.push(...findOxideFiles(packagePath));}});}// Search regular node_modulesfiles.push(...findJitiFiles(nodeModules));files.push(...findOxideFiles(nodeModules));return[...newSet(files)];// Remove duplicates};/** * Patch a single file */constpatchFile=(filePath)=>{try{if(!fs.existsSync(filePath)){log(`⚠️ File not found: ${path.basename(filePath)}`,'yellow');returnfalse;}constcontent=fs.readFileSync(filePath,'utf8');consthasNodeImports=content.includes('require("node:')||content.includes("require('node:");if(!hasNodeImports){log(`✅ ${path.basename(filePath)} - already patched`,'green');returntrue;}// Apply patches for both quote stylesconstpatched=content.replace(/require\("node:([^"]+)"\)/g,'require("$1")').replace(/require\('node:([^']+)'\)/g,"require('$1')");fs.writeFileSync(filePath,patched,'utf8');log(`✅ ${path.basename(filePath)} - patched successfully`,'green');returntrue;}catch(error){log(`❌ ${path.basename(filePath)} - error: ${error.message}`,'red');returnfalse;}};/** * Main execution */constmain=()=>{log('🔧 Plasmo + Tailwind v4 compatibility patch','cyan');constfiles=findPackageFiles();if(files.length===0){log('⚠️ No files found to patch','yellow');log(' This might mean packages are not installed or using different structure','yellow');return;}log(` Found ${files.length} files to check`,'blue');constresults=files.map(patchFile);constsuccessful=results.filter(Boolean).length;log('');// Empty lineif(successful===files.length){log('🎉 All files patched successfully!','green');log(' Tailwind v4 should now work with Plasmo','green');}else{log(`⚠️ ${successful}/${files.length} files patched`,'yellow');}if(successful===0){log('💡 Try running: pnpm install && node scripts/patch-jiti.js','blue');}};// Execute if run directlyif(require.main===module){main();}module.exports={ main, patchFile, findPackageFiles };
Based on the comments I ended up writing a script that would patch the files everytime after install. Also helpful if you are sharing code with a team and they need to do the same patch.
scripts/patch.js:
#!/usr/bin/env node
/**
Plasmo + Tailwind v4 Compatibility Patch
Automatically fixes "node:" import issues in jiti and @tailwindcss/oxide
that cause Plasmo builds to fail when using Tailwind CSS v4.
Main execution
*/
const main = () => {
log('🔧 Plasmo + Tailwind v4 compatibility patch', 'cyan');
const files = findPackageFiles();
if (files.length === 0) {
log('⚠️ No files found to patch', 'yellow');
log(' This might mean packages are not installed or using different structure', 'yellow');
return;
}
log( Found ${files.length} files to check, 'blue');
if (successful === files.length) {
log('🎉 All files patched successfully!', 'green');
log(' Tailwind v4 should now work with Plasmo', 'green');
} else {
log(⚠️ ${successful}/${files.length} files patched, 'yellow');
}
Based on the comments I ended up writing a script that would patch the files everytime after install. Also helpful if you are sharing code with a team and they need to do the same patch.根据大家的反馈,我最终编写了一个脚本,每次安装后都会自动修补文件。如果你与团队共享代码,而他们也需要进行同样的修补,这个脚本也很有用。
scripts/patch.js:scripts/patch.js :
#!/usr/bin/env node
/**
Plasmo + Tailwind v4 Compatibility Patch
Automatically fixes "node:" import issues in jiti and @tailwindcss/oxide
that cause Plasmo builds to fail when using Tailwind CSS v4.
Main execution
*/
const main = () => {
log('🔧 Plasmo + Tailwind v4 compatibility patch', 'cyan');
const files = findPackageFiles();
if (files.length === 0) {
log('⚠️ No files found to patch', 'yellow');
log(' This might mean packages are not installed or using different structure', 'yellow');
return;
}
log( Found ${files.length} files to check, 'blue');
if (successful === files.length) {
log('🎉 All files patched successfully!', 'green');
log(' Tailwind v4 should now work with Plasmo', 'green');
} else {
log(⚠️ ${successful}/${files.length} files patched, 'yellow');
}
I found this helpful if you are using turborepo because the folder structure is different:
#!/usr/bin/env node
/** * Plasmo + Tailwind v4 Compatibility Patch (Monorepo-aware) * * Fixes "node:" import issues in jiti and @tailwindcss/oxide. * Run from ANYWHERE in your monorepo — it finds the root automatically. */constfs=require("fs")constpath=require("path")constc={reset: "\x1b[0m",red: "\x1b[31m",green: "\x1b[32m",yellow: "\x1b[33m",blue: "\x1b[34m",cyan: "\x1b[36m",gray: "\x1b[90m"}constlog=(msg,color="reset")=>console.log(`${c[color]}${msg}${c.reset}`)/** * Find monorepo root by looking for pnpm-workspace.yaml or root package.json */functionfindMonorepoRoot(startDir=process.cwd()){letcurrent=path.resolve(startDir)while(current!==path.dirname(current)){if(fs.existsSync(path.join(current,"pnpm-workspace.yaml"))){returncurrent}// Also check for root package.json without workspace file (some setups)if(fs.existsSync(path.join(current,"package.json"))){constpkg=JSON.parse(fs.readFileSync(path.join(current,"package.json"),"utf8"))if(pkg.workspaces||fs.existsSync(path.join(current,"pnpm-workspace.yaml"))){returncurrent}}current=path.dirname(current)}// Fallback: just use cwdreturnprocess.cwd()}/** * Recursively find all files matching a pattern in a directory */functionfindFiles(dir,matcher){constresults=[]try{constentries=fs.readdirSync(dir,{withFileTypes: true})for(constentryofentries){constfullPath=path.join(dir,entry.name)if(entry.isDirectory()){results.push(...findFiles(fullPath,matcher))}elseif(matcher(fullPath)){results.push(fullPath)}}}catch{// Permission denied or not a directory}returnresults}/** * Find jiti files in pnpm store */functionfindJitiFiles(rootNodeModules){constfiles=[]constpnpmDir=path.join(rootNodeModules,".pnpm")if(!fs.existsSync(pnpmDir)){log("No .pnpm directory found. Are you using pnpm?","yellow")returnfiles}constentries=fs.readdirSync(pnpmDir)for(constentryofentries){// pnpm stores packages as "jiti@2.7.0" or "jiti@2.7.0_something" (peer deps)if(entry.startsWith("jiti@")){constpackageRoot=path.join(pnpmDir,entry,"node_modules","jiti")consttargets=[path.join(packageRoot,"dist","jiti.cjs"),path.join(packageRoot,"dist","babel.cjs"),path.join(packageRoot,"lib","jiti.cjs")]for(consttargetoftargets){if(fs.existsSync(target)){files.push(target)}}}}returnfiles}/** * Find @tailwindcss/oxide files */functionfindOxideFiles(rootNodeModules){constfiles=[]constpnpmDir=path.join(rootNodeModules,".pnpm")if(!fs.existsSync(pnpmDir))returnfilesconstentries=fs.readdirSync(pnpmDir)for(constentryofentries){// Handle both @tailwindcss+oxide@ and %40tailwindcss+oxide@if(entry.includes("tailwindcss")&&entry.includes("oxide")){constpackageRoot=path.join(pnpmDir,entry,"node_modules","@tailwindcss","oxide")consttarget=path.join(packageRoot,"index.js")if(fs.existsSync(target)){files.push(target)}}}returnfiles}/** * Patch a single file */functionpatchFile(filePath){try{if(!fs.existsSync(filePath)){log(`⚠️ Not found: ${filePath}`,"yellow")returnfalse}constcontent=fs.readFileSync(filePath,"utf8")// Check if already patchedif(!content.includes('require("node:')&&!content.includes("require('node:")){log(`⏭️ ${path.relative(process.cwd(),filePath)} — no node: imports found`,"gray")returntrue}constpatched=content.replace(/require\("node:([^"]+)"\)/g,'require("$1")').replace(/require\('node:([^']+)'\)/g,"require('$1')")fs.writeFileSync(filePath,patched,"utf8")log(`✅ Patched: ${path.relative(process.cwd(),filePath)}`,"green")returntrue}catch(error){log(`❌ Error patching ${filePath}: ${error.message}`,"red")returnfalse}}/** * Main */functionmain(){constroot=findMonorepoRoot()constrootNodeModules=path.join(root,"node_modules")log("🔧 Plasmo + Tailwind v4 compatibility patch","cyan")log(` Monorepo root: ${root}`,"blue")log(` Node modules: ${rootNodeModules}`,"blue")log("")if(!fs.existsSync(rootNodeModules)){log("❌ node_modules not found. Run pnpm install first.","red")process.exit(1)}constjitiFiles=findJitiFiles(rootNodeModules)constoxideFiles=findOxideFiles(rootNodeModules)constallFiles=[...newSet([...jitiFiles, ...oxideFiles])]if(allFiles.length===0){log("⚠️ No jiti or @tailwindcss/oxide files found.","yellow")log(" Possible reasons:","yellow")log(" • Packages aren't installed (run pnpm install)","yellow")log(" • Different package versions than expected","yellow")log(" • pnpm virtual store is in a non-standard location","yellow")return}log(` Found ${allFiles.length} file(s) to check`,"blue")log("")constresults=allFiles.map(patchFile)constpatched=results.filter(Boolean).lengthlog("")if(patched===allFiles.length){log(`🎉 All ${allFiles.length} files OK!`,"green")}else{log(`⚠️ ${patched}/${allFiles.length} files processed`,"yellow")}}if(require.main===module){main()}module.exports={ main, findMonorepoRoot, patchFile }
Activity
thekayshawn commentedon Feb 17, 2025
+1 on this, got a monorepo setup with 4 apps using the same shared design system with tailwind v4, have to make the PR wait until this gets resolved otherwise our extension will break.
Jemeni11 commentedon Feb 17, 2025
Same here ✋
BalutaAlex commentedon Feb 17, 2025
Probably related to parcel-bundler/parcel#9244. The issue has been fixed in newer parcel versions it seems so we should get forward with updating to a newer parcel version
fix: 升级tailwindcss到3版本最后一版,4版本需要等待plasmo支持(PlasmoHQ/plasmo#1188)
shinauri commentedon Mar 6, 2025
Has anyone been able to solve the problem?
Xheldon commentedon Mar 7, 2025
Has anyone been able to solve the problem?
ctrhub commentedon Mar 7, 2025
Fixed this issue by downgrading these packages to the following versions:
Also created
postcss.config.jsin the root folder:And created
globals.cssin the root folder:peguimasid commentedon Mar 7, 2025
@ctrhub The issue here is specifically related to upgrading Tailwind to version 4. The code you provided is using Tailwind version 3, which currently works fine with Plasmo.
ObinnaAka commentedon Mar 18, 2025
So I found a hacky way around it. You can go into your node_modules folder and look for the file at
...node\_modules/@tailwindcss/node/node\_modules/jiti/dist/jiti.cjsYou want to manually remove the
node:...prefix. You'll need to do this about a dozen more times throughout the node package.This is a naming convention in recent node versions. I'm working to find a more permanent/reasonable solution (probably involving an alias is my guess)
ObinnaAka commentedon Mar 18, 2025
Got the answer. You have to patch the package (for now)
In my case, I use bun.sh, so:
bun patch jiti@2.4.2but with npm, it would be
And then you want to manually go into your node modules and perform the steps above: find the references to
"node:modules"that are mentioned in the error message and replace it with"modules".You'll need to do it for some other
"node:...references as well. Just follow the plasmo console error message.Hopefully we get a better fix soon.
shawnlikescode commentedon Mar 19, 2025
I can't find the file you're talking about. Can you explain some more?
ObinnaAka commentedon Mar 19, 2025
All good! I'll go in depth.
So for example, the original post had this error
You want to go to the file at this path (replace it with your own path)
/Users/ ...<your own path>... /node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/lib/jiti.cjsAnd then you want to search for
"node:modules"inside the file, and replace it with"modules"You will need to repeat this with other similar import like
"node:os""node:fs""node:..."Make sure your plasmo dev server keeps running when you do this. The error message will tell you what file needs to be changed next. Once you've changed all the references, then your extension should build!
After that, then you can follow the instructions above to patch you package.json
Hope this helps!
shawnlikescode commentedon Mar 19, 2025
Thank you!
Can you share one of the edits?
I tried I still get an error in the file.
🔴 ERROR | Build failed. To debug, run plasmo dev --verbose.
🔴 ERROR | Could not resolve module "modules" from "*/node_modules/.pnpm/jiti@2.4.2/node_modules/jiti/lib/jiti.cjs"
ObinnaAka commentedon Mar 19, 2025
Oh, stop and restart your dev server each time. Apologies, I should have clarified.
I don't think Parcel picks up changes in the node_modules folder without a restart
5 remaining items
tinacious commentedon Apr 13, 2025
Thanks @ObinnaAka for this! I am using pnpm and did the following:
pnpm patch jiti@2.4.2.node_modules/.pnpm_patches/jiti@2.4.2, I did a find and replace, finding all"node:and replacing with"(so as to remove thenode:as suggested).pnpm patch-commit node_modules/.pnpm_patches/jiti@2.4.2.Works great, thanks! I appreciate you taking the time to share your fix.
constantx commentedon Apr 23, 2025
The patch approach is not very sustainable, nor working in my case. Any plan to support tailwind v4?
vantezzen commentedon Apr 24, 2025
For anyone unfamiliar with patching in pnpm, here's a more detailed guide for Plasmo and Tailwind 4: https://gist.github.com/vantezzen/f799643aebbfd5522ce87bababb85c5d
No Tailwind v4 :( But here's Inter
Emmanuel-Tyty commentedon May 4, 2025
i added this to the tailwind config
mode: "jit",vslowslow commentedon Jun 24, 2025
any update on this isse?
coder-xiaotian commentedon Jul 1, 2025
same problem
erayerdin commentedon Jul 5, 2025
Yep, still the same problem
rowan-fan commentedon Sep 27, 2025
Same problem
architgarg commentedon Oct 11, 2025
+1
architgarg commentedon Oct 11, 2025
Based on the comments I ended up writing a script that would patch the files everytime after install. Also helpful if you are sharing code with a team and they need to do the same patch.
scripts/patch.js:
Then in package.json:
showwwwww commentedon Oct 12, 2025
Perfectly resolve! I admit you're the best handsome man in 2025!!!
Ying-Luan commentedon Dec 20, 2025
Perfectly solved! Brilliant solution, thank you so much for the help!
wodepig commentedon Apr 10, 2026
Fortunately, I didn't replace it manually, but looked down for the code that was automatically replaced.🤣 solution, thank you
derick-kibiwott commentedon Jul 7, 2026
I found this helpful if you are using turborepo because the folder structure is different: