layer5io / layer5io/layer5

Warnings when running `npm run build`

Open
#7,606 4 comments 0 reactions 1 assignee View on GitHub

@mansiverma897993 is already working on this.

Since Apr 9, 2026.

area/ci framework/gatsby help wanted kind/bug
Dominant language
JavaScript
Stars
1.1k
Forks
1.6k
Avg merge
2d 10h
Merged PRs (30d)
18

Description

Description
warning There are routes that match both page and redirect. Pages take precedence over redirects so the redirect will not work:
 - page: "/learn/learning-paths/mastering-kubernetes-for-engineers" and redirect: "/learn/learning-paths/mastering-kubernetes-for-engineers/" -> "/learn/learning-paths/mastering-kubernetes-for-engineers"
 - page: "/learn/learning-paths/mastering-meshery" and redirect: "/learn/learning-paths/mastering-meshery/" -> "/learn/learning-paths/mastering-meshery"
 - page: "/learn/learning-paths/mastering-kubernetes-for-engineers/ambassador-edge-stack-api-gateway-with-meshery" and redirect: "/learn/learning-paths/mastering-kubernetes-for-engineers/ambassador-edge-stack-api-gateway-with-meshery/" -> "/learn/learning-paths/mastering-kubernetes-for-engineers/ambassador-edge-stack-api-gateway-with-meshery"
 - page: "/learn/learning-paths/mastering-service-meshes-for-developers" and redirect: "/learn/learning-paths/mastering-service-meshes-for-developers/" -> "/learn/learning-paths/mastering-service-meshes-for-developers"
 - page: "/learn/learning-paths/mastering-kubernetes-for-engineers/deploying-wordpress-and-mysql-with-persistent-volumes-with-meshery" and redirect: "/learn/learning-paths/mastering-kubernetes-for-engineers/deploying-wordpress-and-mysql-with-persistent-volumes-with-meshery/" -> "/learn/learning-paths/mastering-kubernetes-for-engineers/deploying-wordpress-and-mysql-with-persistent-volumes-with-meshery"
 - page: "/learn/learning-paths/mastering-kubernetes-for-engineers/explore-dapr-with-meshery" and redirect: "/learn/learning-paths/mastering-kubernetes-for-engineers/explore-dapr-with-meshery/" -> "/learn/learning-paths/mastering-kubernetes-for-engineers/explore-dapr-with-meshery"
 - page: "/learn/learning-paths/mastering-kubernetes-for-engineers/scalable-postgres-with-cloudnativepg" and redirect: "/learn/learning-paths/mastering-kubernetes-for-engineers/scalable-postgres-with-cloudnativepg/" -> "/learn/learning-paths/mastering-kubernetes-for-engineers/scalable-postgres-with-cloudnativepg"
 - page: "/learn/learning-paths/mastering-meshery/introduction-to-meshery" and redirect: "/learn/learning-paths/mastering-meshery/introduction-to-meshery/" -> "/learn/learning-paths/mastering-meshery/introduction-to-meshery"
 - page: "/learn/learning-paths/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh" and redirect: "/learn/learning-paths/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh/" -> "/learn/learning-paths/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh"
 - page: "/learn/learning-paths/mastering-service-meshes-for-developers/introduction-to-service-meshes" and redirect: "/learn/learning-paths/mastering-service-meshes-for-developers/introduction-to-service-meshes/" -> "/learn/learning-paths/mastering-service-meshes-for-developers/introduction-to-service-meshes"
 - page: "/learn/learning-paths/mastering-kubernetes-for-engineers/ambassador-edge-stack-api-gateway-with-meshery/edge/conclusion" and redirect: "/learn/learning-paths/mastering-kubernetes-for-engineers/ambassador-edge-stack-api-gateway-with-meshery/edge/conclusion/" -> "/learn/learning-paths/mastering-kubernetes-for-engineers/ambassador-edge-stack-api-gateway-with-meshery/edge/conclusion"

Expected Behaviour

There should be clean build

Screenshots
Environment:
  • Host OS:
  • Browser:

Contributor Resources and Handbook

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

Join the Layer5 Community by submitting your community member form.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.