As far as I understand it this should be a valid layout v1 convention:

• auth
  • login.tsx site.com/login.tsx
• dashboard
  • index.tsx site.com/
  • about.tsx site.com/about
• __auth.tsx
• __dashboard.tsx

However when using this package to keep compatibility to move to v2 elsewhere we get an error:

What version of Remix are you using?

1.17.0

Are all your remix dependencies & dev-dependencies using the same version?

• Yes

Steps to Reproduce

• Install 1.17.0
• Configure v2_routeConvention with @remix-run/v1-route-convention
• Run project
• Add a route
• After a very long rebuild time (issue already created before) the route isn't registered

Precision : Do not use the new dev server but the historic one.

Expected Behavior

The route is registered and accessible without full reload of dev server.

Actual Behavior

The route is not registered.

What version of Remix are you using?

2.0.0 (or trying to)

Are all your remix dependencies & dev-dependencies using the same version?

• Yes

Steps to Reproduce

npx upgrade-remix 2.0.0

On a 1.19.3 project with v1-meta and v1-route-convention both installed.

Expected Behavior

Upgrade goes ahead.

Actual Behavior

npm install fails:

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: reset-apollo@undefined
npm WARN Found: @remix-run/[email protected]
npm WARN node_modules/@remix-run/dev
npm WARN   peer @remix-run/dev@"^1.15.0" from @remix-run/[email protected]
npm WARN   node_modules/@remix-run/v1-route-convention
npm WARN     @remix-run/v1-route-convention@"^0.1.2" from the root project
npm WARN   1 more (the root project)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @remix-run/dev@"^1.15.0" from @remix-run/[email protected]
npm WARN node_modules/@remix-run/v1-route-convention
npm WARN   @remix-run/v1-route-convention@"^0.1.2" from the root project
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @remix-run/[email protected]
npm ERR! Found: @remix-run/[email protected]
npm ERR! node_modules/@remix-run/react
npm ERR!   @remix-run/react@"2.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @remix-run/react@"^1.15.0" from @remix-run/[email protected]
npm ERR! node_modules/@remix-run/v1-meta
npm ERR!   @remix-run/v1-meta@"^0.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @remix-run/[email protected]
npm ERR! node_modules/@remix-run/react
npm ERR!   peer @remix-run/react@"^1.15.0" from @remix-run/[email protected]
npm ERR!   node_modules/@remix-run/v1-meta
npm ERR!     @remix-run/v1-meta@"^0.1.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Hi,
it seems the v1-route-convention package is causing problems when using the unstable_vitePlugin (see remix-run/remix#8585).
I just spend half a day figuring out why the local dev server was stopping unexpectedly and after removing the v1-route-convention package (as described in the above issue it finally starts, but the project is obviously broken now as we haven't migrated to the v2 route convention yet.
Before we do that however I was wondering if there are any plans on making the package compatible with the vitePlugin?

Created a repo to reproduce here:
https://github.com/cliffordfajardo/remix_express_v1_to_v2_routes_bug

Steps to Reproduce

1. Create a Remix app using V1** (I chose the express template in my repo)

npx [email protected]

3. Update all @remix-run/* dependencies to version 2.0.1
4. Add @remix-run/v1-route-convention package to continue using V1 routes
5. Update remix.config.js to use @remix-run/v1-route-convention package
6. Run npm run dev & the error will appear

💿  remix dev

Error: Error loading Remix config at /Users/cfajardo/Desktop/remix_express_v1_to_v2_routes_bug/remix.config.js
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/cfajardo/Desktop/remix_express_v1_to_v2_routes_bug/node_modules/@remix-run/dev/dist/config/routes' imported from /Users/cfajardo/Desktop/remix_express_v1_to_v2_routes_bug/node_modules/@remix-run/v1-route-convention/dist/index.mjs
Did you mean to import @remix-run/dev/dist/config/routes.js?
    at Object.readConfig (/Users/cfajardo/Desktop/remix_express_v1_to_v2_routes_bug/node_modules/@remix-run/dev/dist/config.js:72:13)
    at async Object.dev (/Users/cfajardo/Desktop/remix_express_v1_to_v2_routes_bug/node_modules/@remix-run/dev/dist/cli/commands.js:179:18)
    at async Object.run (/Users/cfajardo/Desktop/remix_express_v1_to_v2_routes_bug/node_modules/@remix-run/dev/dist/cli/run.js:192:7)

NOTE: all of these steps have been applied is in the bug reproduction repo:
https://github.com/cliffordfajardo/remix_express_v1_to_v2_routes_bug

I'm in the process of upgrading my project to ESM but am running into this issue:

Cannot find module 'node_modules\@remix-run\dev\dist\config\routes' imported from node_modules\@remix-run\v1-route-convention\dist\index.mjs

In my remix.config.js I import it like this: import { createRoutesFromFolders } from '@remix-run/v1-route-convention';

It worked fine in cjs land but now I'm stuck.

Error: Error loading Remix config at remix.config.js
Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'node_modules\@remix-run\dev\dist\config\routes' imported from node_modules\@remix-run\v1-route-convention\dist\index.mjs
Did you mean to import @remix-run/dev/dist/config/routes.js?
    at Object.readConfig (node_modules\@remix-run\dev\dist\config.js:76:13)
    at async Object.watch (node_modules\@remix-run\dev\dist\cli\commands.js:216:78)
    at async Object.run (node_modules\@remix-run\dev\dist\cli\run.js:498:7)