Bug report

Describe the bug

When running next using Yarn 2 and visiting a page in the browser that doesn't exist, the 404 error page never shows up. Instead it loads forever ("waiting on localhost...") and then eventually errors with ERR_EMPTY_RESPONSE.

But the terminal shows that the page was compiled:

[ event ] build page: /next/dist/pages/_error
[ wait ]  compiling ...

macOS version:
10.14.6 (18G95)

Kap version:
3.0.0-beta.6

Other possibly relevant info:
Monitor setup: single rMBP 15" screen, no external monitors
macOS scrollbar appearance setting: "Show Always" (in System Preferences > General)

Steps to reproduce

1. Click the Kap menu bar icon.
2. Click the button in the Kap bar to record an area of the screen.
3. Select a regio

Description

The form UI provides no indicator when saving fails.

Steps to reproduce

1. Go to a Ga

It would be great to have this project as video series or as step by step tutorial where you learn bit by bit and have a functional product in the end.

this website 0x0.st holds files/shortens urls temporary and can be easily summoned via the terminal with curl, i was looking for way of shortening kutt just like this...

the answer was probably in Bash: Simple command line program for Kutt but the link seems to be broken.

Are there any documentation on how to deploy this to production? right now if you look at the source code, bunch of codes __NEXT_DATA__ I want to see if these codes are gone in production.

has anyone deployed the front-end to digital ocean?

EDIT: See this comment below on what to document.

What is the problem?

Cannot add dependencies to packages

Steps to Reproduce:

1. Pull canary
2. yarn
3. cd ./examples/server
4. yarn add --dev metro-memory-fs
5. Get Yarn error:

blitz/packages/server on  canary [$] via ⬢ v12.16.1

Just tested this.

If I add .add('redirect', '/test-route/:queryparams') to routes, links like:

http://localhost/test-route?queryparams=param

work, if I put .add('test-route', '/test-route/:queryparams', 'test-other-route') the link above leads to a 404. Only links like:

http://localhost/test-route/param

Will work. Is this intended behavior?

It would be really cool to have a section below in the readme to showcase projects built with RAN, or at least maybe somewhere where people can add links to their projects that they've built with this framework! (SUGGESTION)

Some folks have noted it would be beneficial to have this repository translated to other languages. One contributor has already volunteered to translate the repository into Russian (woohoo!).

If anyone has the time and drive to help out with other languages, please reply below with the proposed language and I'll give you the "go-ahead"... just to make sure two people don't create translations i

I'm not sure if this will be included when the book is finished, but getting the config values for the .env file requires getting values from a lot of different sources and different configurations. It would be helpful if there was better documentation around that process.

I would love to submit a PR for it, but I haven't been able to figure all of it out myself yet.

Is your feature request related to a problem? Please describe.

Right now as far as I could see, there is no documentation about how to integrate with Locize.

Describe the solution you'd like

I'd super helpful describe it or to have a simple Locize code example.

Describe alternatives you've considered

Can't find anything

if you modify the swDest option to generate the serviceworker in other path, this not affect the path to generate the development service-worker.

I need to see the code to fix this, but would be nice to have this in the documentation.
this is the fix to generate serviceworker in development in the right path.

  dontAutoRegisterSw: true,
  devSwSrc: {
    from: './public/sw-dev.js'

sls remove does not remove the S3 bucket.
When I do sls deploy again, it throws BucketName already exists.

Might be nice. Doesn't need to be a number - how bout a Twitter circle?

• Tailwind >=1.4.0 has built-in purgecss support
• Hence, purgecss does not need to be explicitly installed + configured in postcss.config.js

Do we maybe want to update the example under the Customizing PostCSS Config section in the Styling Tips page?

We started this project not quite long after Next.js became public and we haven't really touched the README 😅

We've just been improving the code section and making it a lot better. I guess it's time to give the README a new structure, basically to pass the right message to new users.

Let's do this! 🚀

There is an import dependencie cycle between:

src/Interfaces/index.ts:
export * from '@Redux/IStore';

and

src/Redux/IStore.d.ts:
import { IHomePage } from '@Interfaces';

Eslint rule that detect the issue:
https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-cycle.md