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
I'm setting up a new project and I haven't defined any route data yet. Running tsc -b generates the data-build folder, but not the routes subfolder because there are no files yet.
Running npm run dev gives the following error:
[0] Error: ENOENT: no such file or directory, scandir '...project path...\data-build\routes'
[0] at Object.readdirSync (node:fs:1044:3)
[0] at visitFiles (...project path...\node_modules\@remix-run\core\routesConvention.js:109:47)
[0] at Object.defineConventionalRoutes (...project path...\node_modules\@remix-run\core\routesConvention.js:69:3)
[0] at Object.readConfig (...project path...\node_modules\@remix-run\core\config.js:51:35)
[0] at Object.run (...project path...\node_modules\@remix-run\core\commands.js:36:31)
[0] at Object.<anonymous> (...project path...\node_modules\@remix-run\cli\index.js:47:19)
[0] at Module._compile (node:internal/modules/cjs/loader:1108:14)
[0] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10)
[0] at Module.load (node:internal/modules/cjs/loader:973:32)
[0] at Function.Module._load (node:internal/modules/cjs/loader:813:14)
[0] remix run exited with code 1
From digging into @remix-run/core/routesConvention.js it looks like adding an fs.existsSync(dir) check to visitFiles would be enough to handle the error (and maybe add a console warning to indicate that the directory couldn't be found).
The text was updated successfully, but these errors were encountered:
Details
I'm setting up a new project and I haven't defined any route data yet. Running
tsc -b
generates thedata-build
folder, but not theroutes
subfolder because there are no files yet.Running
npm run dev
gives the following error:From digging into
@remix-run/core/routesConvention.js
it looks like adding anfs.existsSync(dir)
check tovisitFiles
would be enough to handle the error (and maybe add a console warning to indicate that the directory couldn't be found).The text was updated successfully, but these errors were encountered: