one update on this patch better to create an other param , else matchpath feature is broken

    const renderResponse = await renderDevHTML({
      path: pathObj.path, // patch
      pathorigin: decodeURI(req.path), // patch
      page: pathObj,
      skipSsr: req.query[`skip-ssr`] || false,
      store,
      htmlComponentRendererPath: `${program.directory}/public/render-page.js`,
      directory: program.directory
    });

<!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. -->

<!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation -->

<!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc
• I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if applicable)
• I have added necessary documentation (if applicable)
• Any dependent changes have been merged and published in downstream modules -->

Proposed changes (including videos or screenshots)

<!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. -->

<!-- END CHANGELOG -->

Issue(s)

<!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 -->

Steps to test or reproduce

<!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable -->

Further comments

<!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->

<!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. -->

<!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation -->

<!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc
• I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if applicable)
• I have added necessary documentation (if applicable)
• Any dependent changes have been merged and published in downstream modules -->

Proposed changes (including videos or screenshots)

<!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. -->

<!-- END CHANGELOG -->

Issue(s)

<!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 -->

Steps to test or reproduce

<!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable -->

Further comments

<!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->

@dotansimha I have merged master and resolved the conflicts now. 🙂 Thanks!

A link path is not correctly rendered in ssr compared to client

solution to patch in src/utils/find-path.js

var here potentialPatho save the correct replace path

if (path !==/) { // check various trailing/leading slashes combinations const hasLeadingSlash = path.startsWith(/); const hasTrailingSlash = path.endsWith(/); const bare = path.slice(hasLeadingSlash ? 1 : 0, hasTrailingSlash ? -1 : path.length); let potentialPatho; [bare,/+ bare, bare +/,/+ bare +/`].some(potentialPath => { page = pages.get(potentialPath); potentialPatho=potentialPath; return !!page; });

  if (page) {
  page.path=potentialPatho;
    return page;
  }
} `

@esilverm: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

We no longer support using JSON for setting or storing request headers.

When setting up the monorepo, following the Gatsby local development instructions, the linting portion of yarn test failed on gatsby-plugin-preact and gatsby-plugin-gatsby-cloud. The following files were via eslint errors when running yarn test:

• gatsby/packages/gatsby-plugin-gatsby-cloud/components/GatsbyIndicatorButton.js
• gatsby/packages/gatsby-plugin-gatsby-cloud/components/Indicator.js
• gatsby/packages/gatsby-plugin-gatsby-cloud/components/IndicatorButton.js
• gatsby/packages/gatsby-plugin-gatsby-cloud/components/IndicatorButtonTooltip.js
• gatsby/packages/gatsby-plugin-gatsby-cloud/components/InfoIndicatorButton.js
• gatsby/packages/gatsby-plugin-gatsby-cloud/components/LinkIndicatorButton.js
• gatsby/packages/gatsby-plugin-gatsby-cloud/components/Style.js
• gatsby/packages/gatsby-plugin-gatsby-cloud/utils/getBuildInfo.js
• gatsby/packages/gatsby-plugin-gatsby-cloud/utils/trackEvent.js
• gatsby/packages/gatsby-plugin-preact/fast-refresh/formatWebpackErrors.js
• gatsby/packages/gatsby-plugin-preact/fast-refresh/prefreshGlueCode.js

I reviewed this with @pieh mid last week, and he indicated these should be excluded during yarn test on the monorepo.

Description

Excludes the two mentioned packages from linting when setting up the monorepo for local development.

Documentation

No documentation updates required. This change purely removes unnecessary linting.

Related Issues

There are no related issues.

<!-- Have any questions? Check out the contributing docs at https://gatsby.dev/contribute, or ask in this Pull Request and a Gatsby maintainer will be happy to help :) -->

<!-- Is this a blog post? Check out the docs at https://www.gatsbyjs.com/contributing/blog-contributions/, and please mention if the blog post is pre-approved by someone from Gatsby. -->

Description

<!-- Write a brief description of the changes introduced by this PR -->

Documentation

<!-- Where is this feature or API documented?

• If docs exist:
  • Update any references, if relevant. This includes Guides and Gatsby Internals docs.
• If no docs exist:
  • Create a stub for documentation including bullet points for how to use the feature, code snippets (including from happy path tests), etc.
• Tag @gatsbyjs/documentation for review, pairing, polishing of the documentation -->

Related Issues

<!-- Link to the issue that is fixed by this PR (if there is one) e.g. Fixes #1234

Link to an issue that is partially addressed by this PR (if there are any) e.g. Addresses #1234

Link to related issues (if there are any) e.g. Related to #1234 -->

This is not stale (I provided a minimal reproduction and haven't heard anything since).

Thanks, I changed it but the word shown when hovering the Home icon is still the wrong one.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/inquirer	7.3.1 -> 7.3.2

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

The latest changes of this PR are available as alpha in npm (based on the declared changesets):

⚠️ No Changeset found

Latest commit: ef96d9602655dafde9ce0cea97ab03391c3b531c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

<details><summary>This PR includes no changesets</summary>

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

</details>

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/inquirer	7.3.1 -> 7.3.2

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

Description

Removes the generation of a polyfill if all the browsers support ES6 modules. This should have a few benefits:

1. Reduce confusion in discussions, see https://github.com/gatsbyjs/gatsby/issues/28736, https://github.com/gatsbyjs/gatsby/issues/26894 etc
2. Reduce noise in bundle analysis tools like webpack-bundle-analyzer. It still gets generated and therefore displayed.
3. Reduce files webpack has to produce and then subsequently get deployed

The implementation simply uses the browserslist and checks whether there are any browsers that do not support ES6 modules. If there are then include the polyfills.

What's going on? Running npx ignite-cli new PizzaApp --expo will result into the following error:

/usr/local/lib/node_modules/ignite-cli/node_modules/gluegun/build/index.js:13
    throw up;
    ^
mv: no such file or directory: /home/xxx/Projects//PizzaApp/ios/PizzaApp
mv: no such file or directory: /home/xxx/Projects/PizzaApp/ios/PizzaApp-tvOS
mv: no such file or directory: /home/xxx/Projects/PizzaApp/ios/PizzaApp-tvOSTests
mv: no such file or directory: /home/xxx/Projects/PizzaApp/ios/PizzaApp.xcodeproj
mv: no such file or directory: /home/xxx/Projects/PizzaApp/ios/PizzaApp.xcodeproj/xcshareddata/xcschemes/PizzaApp-tvOS.xcscheme
mv: no such file or directory: /home/xxx/Projects/PizzaApp/ios/PizzaApp.xcodeproj/xcshareddata/xcschemes/PizzaApp.xcscheme
mv: no such file or directory: /home/xxx/Projects/PizzaApp/ios/PizzaAppTests
mv: no such file or directory: /home/xxx/Projects/PizzaApp/ios/PizzaAppTests/PizzaAppTests.m
mv: no such file or directory: /home/xxx/Projects/PizzaApp/ios/PizzaApp.xcworkspace
mv: no such file or directory: /home/xxx/Projects/PizzaApp/ios/PizzaApp/PizzaApp.entitlements
mv: no such file or directory: /home/xxx/Projects/PizzaApp/ios/PizzaApp-Bridging-Header.h
node:internal/process/promises:246
          triggerUncaughtException(err, true /* fromPromise */);
          ^

[Error: ENOENT: no such file or directory, open '/home/xxx/Projects/PizzaApp/android/app/src/main/AndroidManifest.xml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/xxx/Projects/PizzaApp/android/app/src/main/AndroidManifest.xml'
}

(Use `node --trace-uncaught ...` to show where the exception was thrown)

Steps to reproduce

1.npx ignite-cli new PizzaApp --expo

ignite doctor results:

  node                                 16.1.0       /usr/local/bin/node 
  npm                                  7.16.0       /usr/local/bin/npm  
    @vue/cli-service-global            4.5.13                           
    @vue/cli                           4.5.13                           
    @wessberg/cjs-to-esm-transformer   0.0.22                           
    bower                              1.8.12                           
    devenvgenerator                    -                                
    expo-cli                           4.5.2                            
    fauna-shell                        0.12.3                           
    generator-generator                4.0.2                            
    generator-oxid-4-aks               -                                
    ignite-cli                         7.0.3                            
    lambda-local                       1.7.4                            
    latest                             0.2.0                            
    n                                  7.2.2                            
    nativescript                       8.0.2                            
    netlify-cli                        3.13.10                          
    npm-check-updates                  11.7.1                           
    npm                                7.16.0                           
    pnpm                               5.18.9                           
    pure-prompt                        1.16.0                           
    react-native-cli                   2.0.1                            
    typescript                         4.2.4                            
    vercel                             22.0.1                           
    yarn                               1.22.10                          
    yo                                 3.1.1                            
  yarn                                 1.22.10      /usr/local/bin/yarn 

Ignite
  ignite-cli         7.0.3        /usr/local/bin/ignite                        
  ignite src         build        /usr/local/lib/node_modules/ignite-cli/build 

Android
  java               15.0.3       /usr/bin/java          
  android home       -            /home/alex/Android/Sdk 

Any ideas?