-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.12 ENOENT: no such file or directory
referencing outes
instead of routes
#5322
Comments
I'm not seeing this problem on my side, having just created a new project using Could you detail the exact steps you're using to create the app? |
I've tried to recreate with a new init and I can't seem to. But I can't fix my current instance either. I've deleted the package lock file and node modules, and can't see why or what is causing this issue. Another strange issue. I can't build either;
If you look at the log it looks like the I've pushed up this repo. It's pretty close to vanilla Remix. All I've done is add basic tailwind config as per your docs, opted into v2 route convention, and created a couple of super simple components. Are you able to run the following steps;
|
Same here. I'm using remix with express.
Looks like this
should be:
or something. This PR: |
I had two dev dependencies which I forgot to update. This fixed the issue.
|
@sockthedev I'm 99% sure that you have an unaligned remix dependency, like @madispuk had. You can do |
Hmmm, I was hopeful after that comment but the grep appears fine?
My package.json dependencies; {
"dependencies": {
"@remix-run/node": "^1.12.0",
"@remix-run/react": "^1.12.0",
"@remix-run/serve": "^1.12.0",
"isbot": "^3.6.5",
"react": "^18.2.0",
"react-dom": "^18.2.0"
},
"devDependencies": {
"@remix-run/dev": "^1.12.0",
"@remix-run/eslint-config": "^1.12.0",
"@types/react": "^18.0.25",
"@types/react-dom": "^18.0.8",
"eslint": "^8.27.0",
"npm-run-all": "^4.1.5",
"prettier": "^2.8.3",
"tailwindcss": "^3.2.4",
"typescript": "^4.9.5"
}
} Versions;
macOS 12.6.1 (Monterey) |
I'm running into a similar issue. I upgraded an existing project to 1.12.0 and can no longer dev/build. It seems to be connected to the v2_routeConvention option. With a fresh new project, the moment I turn on v2_routeConvention, I get the same error as my existing project:
It will lists all the routes files correctly but with the wrong path. The build does complete when I rename the |
Shot in the dark: could you both add Would totally appreciate a public repository reproducing the issue |
Shall try that, here is a public repository in the interim; |
Since I never used pnpm, would you mind updating the README with the actual commands to run using pnpm? 🙏🏼 |
Sure, I'll update it. The commands are;
|
I even tried some resolutions for good measure; {
"resolutions": {
"@remix-run/dev": "1.12.0",
"@remix-run/eslint-config": "1.12.0",
"@remix-run/node": "1.12.0",
"@remix-run/react": "1.12.0",
"@remix-run/serve": "1.12.0",
"@remix-run/server-runtime": "1.12.0"
}
} But still get the following build error, similar to @iamriot-dev the "routes" path is being interpreted as
|
Here's the fresh project I was testing and having issues with: https://github.com/iamriot-dev/test-remix. For what it's worth, I'm using Yarn with PnP instead of pnpm. By the way, you can see the misinterpretation of the paths present itself in the
It is affecting both the file path and route path. |
I've also just ran into this issue and it turned out it was due to unaligned remix dependencies. |
Is
related to
or are these two separate issues? I have also raised the |
I think the first error is a symptom of the issue when running the dev server. |
Awesome, thanks for jumping on this issue so fast! |
I can confirm the same behaviour. It trims the first word of our route,
|
I can confirm the same behavior as well. Updated an existing project to 1.12.0 and it doesn't dev/build. Created a new project using indie stack, everything works great, expect if I try to use the v2 routes. |
This comment was marked as duplicate.
This comment was marked as duplicate.
1.12.0
- can't run remix dev
on a "Remix App Server" instanceoutes
instead of routes
outes
instead of routes
ENOENT: no such file or directory
referencing outes
instead of routes
Closed by #5228 |
🤖 Hello there, We just published version Thanks! |
There were some fixes to thier new v2 filesystem routing that this will help with. Related to remix-run/remix#5322 and remix-run/remix#5228.
There were some fixes to thier new v2 filesystem routing that this will help with. Related to remix-run/remix#5322 and remix-run/remix#5228.
What version of Remix are you using?
1.12.0
Are all your remix dependencies & dev-dependencies using the same version?
Steps to Reproduce
remix dev
The following error occurs;
Expected Behavior
The dev server executes as before.
Actual Behavior
An error occurs on dev server load.
The text was updated successfully, but these errors were encountered: