gatsby-plugin-create-client-paths: Sets matchPath incorrectly for client side path entry #15011
Labels
status: confirmed
Issue with steps to reproduce the bug that’s been verified by at least one reviewer.
type: bug
An issue or pull request relating to a bug in Gatsby
When setting prefixes in the config for
gatsby-plugin-create-client-paths
, it seems that a client side path other than/*
still gets its matchPath set to/*
incorrectly.This means that if a project has two different client side path entry points, say
/*
and/app/*
, even for the second case, pages will reach the entry point for/*
Reproduction is at https://github.com/sidharthachatterjee/gatsby-15011-reproduction
Expected
http://localhost:8000/amhjajk should render Not Found in Index
Actual
http://localhost:8000/amhjajk renders Not Found in App
The text was updated successfully, but these errors were encountered: