Skip to content

public should be relative to the rootDir instead of srcDir #1209

@2wheeh

Description

@2wheeh

Feature Request

Currently, publicDir is relative to srcDir, meaning when srcDir is set to 'src', public files must be placed in src/public. This feels unintuitive since public assets typically live at the root level in most web projects.

Having public assets in src/ creates cognitive overhead since:

  • Most developers expect public files to be at the root level.
  • It breaks convention with other popular frameworks/tools.
  • Static assets conceptually don't belong with source code.

Is your feature request related to a bug?

N/A

What are the alternatives?

Make publicDir relative to rootDir instead of srcDir, allowing the public directory to be placed at root level (e.g., <rootDir>/<publicDir>) while source files are organized in src/.

Additional context

This aligns with conventions from other popular web frameworks (Vue, React, Nextjs etc.) where public assets are typically placed at the root level for better project organization and clarity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions