Fix blitz install for recipes that use the path helper

[itsdillon]

Closes: #3900

What are the changes and their implications?

Check if src/pages directory exists in the installer paths helper, else use the root pages directory.

Bug Checklist

• Changeset added (run pnpm changeset in the root directory)

[changeset-bot]

🦋 Changeset detected

Latest commit: 481ee8a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages

Name	Type
blitz	Patch
@blitzjs/auth	Patch
@blitzjs/next	Patch
@blitzjs/rpc	Patch
@blitzjs/codemod	Patch
@blitzjs/config	Patch
@blitzjs/generator	Patch

Not sure what this means? Click here to learn what changesets are.

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

[maotora]

@dillonraphael Hey nice catch, I was facing the same error trying to install the tailwind recipe.
I just left a comment in one of your files. I think previous versions of blitz were using app/pages or something similar instead of just pages.

[itsdillon]

@dillonraphael Hey nice catch, I was facing the same error trying to install the tailwind recipe. I just left a comment in one of your files. I think previous versions of blitz were using app/pages or something similar instead of just pages.

Thanks so much for the review @maotora. Love seeing the community get involved.

So for the legacy framework (which can be found here https://github.com/blitz-js/legacy-framework), allowed for the pages directory to in the app folder. But for blitz 2.0 this is no longer a case.

[maotora]

Thanks for your response, @dillonraphael!

I just tested this and I found there is another edge case to cover for Tailwindcss to get our coding files which no longer reside at pages or app directories.
We need to update tailwind.config.js content array to reflect the directory change as well.

I came up with something like this which fixed it;

// tailwind.config.js
module.exports = {
  content: ["src/**/*.{js,ts,jsx,tsx}"],
  theme: {
    extend: {},
  },
  plugins: [],
}

Which worked!

[itsdillon]

Good find @maotora. Would you like to open another PR for updating the tailwind recipe (since this is tailwind recipe specific)?

[maotora]

@dillonraphael sure I can do that. Will make a PR and tag you then.

[maotora]

@dillonraphael done I've made a PR: here

[cassilup]

Still experiencing this in 2.0.2.

[Doc0x1]

Still experiencing this in 2.0.3 as well. I haven't tested to make sure but I think this might be an issue for projects that are using the App Router instead of the older Pages system.

[siddhsuresh]

yeah @Doc0x1, that seems likely, we would need to add additional handling to also check for the existence of the app directory in the same area as the change in this PR.