[Feature]: Add basename to remix config file

[zachdtaylor]

What is the new or updated feature that you are suggesting?

Somebody in discord asked if he could set a basename for a Remix app, so all routes would have that basename prepended to them: https://discord.com/channels/770287896669978684/770287896669978687/914576247068188692. I think this is something we could add to the remix.config.js file.

Why should this feature be included?

This would allow more flexibility in configuring a Remix app, giving more power to the developer a la "you own your stack."

[satya-nutella]

Not sure if this feature is in plans but it sounds very useful. I'd love to work on this. I'm new to Remix and any guidance would be awesome

[Vivalldi]

@meehawk , take a look at this line

remix/packages/remix-server-runtime/server.ts

Line 59 in a7712f2

let routes = createRoutes(build.routes);

createRoutes accepts a second parameter: parentId. I believe that's where you'd put a basename

[zachdtaylor]

@meehawk Sorry I didn't see this sooner. Been on vacation the last few days. I was planning on doing this but have you already started?

[satya-nutella]

@zachdtaylor I have started it. I wasn't sure if you're going to work on it. I'm really sorry 🥲

[zachdtaylor]

@meehawk no worries, I should have left a comment saying that I was going to work on it

[yamidsumer]

Hello! This feature is very important to be able to use Remix in my company. Any news?

[kiliman]

@yamidsumer I created a package that will let you mount routes from any folder to any base path

Here's a sample site: https://remix-mount-routes-example.herokuapp.com/

It has links to the package repo and example repo.

[ngbrown]

@kiliman I noticed that the resources, such as the .js bundles, are still coming from the root /build location. I thought the idea for this issue was that the entire application can be configured to be hosted from any random virtual directory or sub-path above root on a server. That's at least how the linked issue #107 described it.

[kiliman]

It's mentioned in the README

Depending on your setup, you may also need to update publicPath and assetsBuildDirectory to include your basePath. This will ensure that your assets will be served properly.

module.exports = {
  ignoredRouteFiles: ['.*'],
  publicPath: `${basePath}/build/`,
  assetsBuildDirectory: `public${basePath}/build`,
  ...
}