Commit activity
Last 12 weeks · 0 commits
Community health
1 of 6 standards met
28
✓README○License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 4 discussions · Last activity 5y ago
See all on GitHub →
This issue is probably wrong in this repo, but I am not sure where to put it. So It is not clear to me, if this is a setup problem, e Next.js issue, or a Preact (compat) thing. When an exception is thrown while rendering a component, there seems to be some retry logic going on, causing multiple subsequently failing renders. I created a page which intentionnaly fails when clicking the "Fail" link: Reproduce: 1. Visit deployed minimal example 2. Open Devtools 3. Click Fail link What I expect (and what is happening with vanilla React + Next.js): On console: 1x 1x 1x 1x 1x On screen: Old page gets "removed" Error page gets rendered instead What happens: On console: 1x 1x 4x 4x 5x 1x On screen: Old page "stays" Error page gets rendered additionally What I find interesting: is outputted once, while the error is reported 4 times. Source of example This is the source of the example, deployed here
Current Behavior no page error, no console output, no term output. Steps to Reproduce (for bugs)
Recent fixes
I don't know if it's a bug, but I wanted to mention it, maybe someone can enlighten me. When running the development version, I see a lot of [object object]s in the dom tree. // edit: after a quick google search I found that issue https://github.com/preactjs/preact/issues/1058 Okay create-react-app uses the babel plugins: transform-react-jsx-source and transform-react-jsx-self by default in none-production builds. Preact doesn't support those "special" attributes and just adds them as a stringified version to the dom. I guess it's fine then :)
Hello, I'm seeing the following error when using a custom babel config, And here's the custom babel config, I was following along in the emotion instructions (v10) https://5faaafd0bd0f3f0008469537--emotion.netlify.app/docs/css-prop#babel-preset
Hi, I've been following this issue https://github.com/preactjs/preact/issues/2574 but could not find any way to fix this myself. I've created a very minimal repo for reproduction that is based off this example and simply does three things: 1. Adds a custom to include the styled components config for SSR 2. Adds a custom to the pages folder, configured as suggested here: https://github.com/vercel/next.js/blob/master/examples/with-styled-components/pages/_document.js 3. Adds a styled component to the index.js / about.js pages e.g. The result is that when navigating between routes (it does not always happen on initial load, you might have to navigate back and forth a couple of times, or trigger HMR... not 100% sure what triggers the warning exactly), you will see a warning in the console for each styled component that looks like this: At this point I am unsure if this is a problem with Preact, Next or styled components, but I felt like this repo might be a good place to start. Example repo: https://github.com/tbgse/preact-next-styled-component
Structured data for AI agents
Repository: developit/nextjs-preact-demo. Description: Next.js 9.3 + Preact = 21kB Stars: 381, Forks: 22. Primary language: JavaScript. Languages: JavaScript (100%). Homepage: https://nextjs-preact.now.sh Open PRs: 0, open issues: 4. Last activity: 5y ago. Community health: 28%. Top contributors: developit, JoviDeCroock, marvinhagemeister, bhgsbatista, osdevisnot, queq1890.