This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• fix(deps): update dependency plausible-tracker to v0.3.9
• fix(deps): update redwood monorepo to v1.5.2 (@redwoodjs/auth, @redwoodjs/core, @redwoodjs/forms, @redwoodjs/graphql-server, @redwoodjs/router, @redwoodjs/web)
• chore(deps): update dependency postcss-loader to v7.3.4
• chore(deps): update dependency prettier-plugin-tailwindcss to ^0.6.0
• chore(deps): update dependency tailwindcss to v3.4.7
• chore(deps): update yarn to v3.8.3
• fix(deps): update dependency classnames to v2.5.1
• fix(deps): update dependency clsx to v1.2.1
• fix(deps): update dependency date-fns to v2.30.0
• fix(deps): update dependency filestack-js to v3.32.3
• fix(deps): update dependency node-fetch to v2.7.0
• fix(deps): update dependency sass to v1.77.8
• chore(deps): update dependency node to v20
• chore(deps): update dependency postcss-loader to v8
• chore(deps): update yarn to v4
• fix(deps): update dependency @headlessui/react to v2
• fix(deps): update dependency clsx to v2
• fix(deps): update dependency date-fns to v3
• fix(deps): update dependency i18next to v23
• fix(deps): update dependency i18next-browser-languagedetector to v8
• fix(deps): update dependency node-fetch to v3
• fix(deps): update dependency react-i18next to v15
• fix(deps): update dependency react-markdown to v9
• fix(deps): update dependency sass-loader to v16
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency postcss to v8.4.31 [security]
• fix(deps): update dependency nodemailer to v6.9.9 [security]
• fix(deps): update dependency @redwoodjs/api to v2 [security]
• chore(deps): update dependency autoprefixer to v10.4.19
• fix(deps): update dependency @headlessui/react to v1.7.19
• fix(deps): update dependency react-markdown to v8.0.7
• fix(deps): update dependency slugify to v1.6.6
• fix(deps): update dependency sass-loader to v13.3.3
• fix(deps): update dependency @heroicons/react to v2
• fix(deps): update react monorepo to v18 (major) (react, react-dom)
• fix(deps): update redwood monorepo to v7 (major) (@redwoodjs/auth, @redwoodjs/core, @redwoodjs/forms, @redwoodjs/graphql-server, @redwoodjs/router, @redwoodjs/web)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

not able to edit home page for location and file name

The new home page looks great!

I ran a quick audit with Axe's developer tools and found 22 issues. I'm happy to get a PR going on this if no one is working on it atm.

Right now a job post would be live on the site forever. This feature would automatically make it inactive after 30 days. The owner can come to the site, or click a link in the email, to extend the "active" time another 30 days.

We've got the <script> tag on the docs site, and I thought it was on the main site as well, but I guess not!

We recently saw a massive dip in sticker requests and I was hoping to see that it's because third party sites stopped linking to the page, but there's no analytics on the page!

Just need to add the following to the :

<script src="https://plausible.io/js/script.outbound-links.js" data-domain="redwoodjs.com" defer></script>

I demoed a very simple todo app using MongoDB + Redwood in the recent RedwoodJS 1.0 meetup.

@thedavidprice suggested it might be a good candidate for the example showcase!

Repo Link: https://github.com/TasinIshmam/Todo-App-Redwood-MongoDB

Hello,

Have you thought about switching normalize.css to modern normalize?
Ive seen many modern projects switching, and it seems like the approach is pretty in line with your target group (devs usually dont use ie 11 nowadays :) )

Repo: https://github.com/sindresorhus/modern-normalize

The issue:

It's a small change but I think it'd help people that might not be 100% with how to set up Supabase in relation to RedwoodJS. The code in the doc's say to set our auth up like the below code, however in newer versions of Redwood AuthProvider is not present on @redwoodjs/auth and we have separated this code out into our src/web/auth.ts file.

Code displayed in doc's:

import { AuthProvider } from '@redwoodjs/auth'
import { createClient } from '@supabase/supabase-js'

import { FatalErrorBoundary, RedwoodProvider } from '@redwoodjs/web'
import { RedwoodApolloProvider } from '@redwoodjs/web/apollo'

import FatalErrorPage from 'src/pages/FatalErrorPage'
import Routes from 'src/Routes'

import './index.css'

const supabaseClient = createClient(process.env.SUPABASE_URL, process.env.SUPABASE_KEY)

const App = () => (
  <FatalErrorBoundary page={FatalErrorPage}>
    <RedwoodProvider titleTemplate="%PageTitle | %AppTitle">
      <AuthProvider client={supabaseClient} type="supabase">
        <RedwoodApolloProvider>
          <Routes />
        </RedwoodApolloProvider>
      </AuthProvider>
    </RedwoodProvider>
  </FatalErrorBoundary>
)

export default App

Suggested amendment:

I would like to suggest that the doc's be changed to reflect the update.

web/src/App.[js/tsx]

import { FatalErrorBoundary, RedwoodProvider } from '@redwoodjs/web'
import { RedwoodApolloProvider } from '@redwoodjs/web/apollo'

import FatalErrorPage from 'src/pages/FatalErrorPage'
import Routes from 'src/Routes'

import { AuthProvider, useAuth } from './auth'

import './index.css'

const App = () => (
  <FatalErrorBoundary page={FatalErrorPage}>
    <RedwoodProvider titleTemplate="%PageTitle | %AppTitle">
      <AuthProvider>
        <RedwoodApolloProvider useAuth={useAuth}>
          <Routes />
        </RedwoodApolloProvider>
      </AuthProvider>
    </RedwoodProvider>
  </FatalErrorBoundary>
)

export default App

Add a section to documentation highlighting that our AuthProvider is in src/web/auth.ts and should look like the below code block:

import { createClient } from '@supabase/supabase-js'

import { createAuth } from '@redwoodjs/auth-supabase-web'

const supabaseClient = createClient(
  process.env.SUPABASE_URL, process.env.SUPABASE_KEY
)

export const { AuthProvider, useAuth } = createAuth(supabaseClient)

Hello,

It seems like you use cloudfront as your cdn, which have brotli compression built-in:

This toggle is in edit cache policy settings that you attached to CF distribution.

Breadcrumb:

CloudFront
Policies
Cache
[uuid]
Edit cache policy

This change should shave off couple KBs on text assets like js/css/svg. Its not much, but its honest gain :-)

A complete database reset works okay, but just re-running the seed file causes this error:

Right now, the site's top navigation bar is fixed, so it doesn't take up space in the document. To compliment this, and mitigate each page/layout having its own offset, a fake navigation bar should be added which takes up the same amount of space as the navbar, pushing content down uniformly.

• - Update all pages and layouts to remove padding/margin used to offset for the navbar (where applicable).
• - Update the navbar's position from fixed to sticky top-0.