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 ...

What problem does this feature solve?

Example use case:
A static generated app with thousands of routes, like an e-commerce having a route for each product.
Apart from scheduling nuxt generate to run periodically and generate all static and dynamic routes, it would be nice to have the possibility to generate the static files for a single route, for example in a hook when the related ba

Looks like app.json is hard-coded in jest-expo https://github.com/expo/expo/blob/d39095cd1b037bd54107a932b05d7261b219df58/packages/jest-expo/src/preset/createMockConstants.js#L47

I've been playing around with Razzle and how the Server HMR works.

I generated a Razzle Project and run it

• npx create-razzle-app my-app
• cd my-app && yarn start

If I now edit the src/Home.js I see hot reloading working in the browser and I see the server.js being re-required by the index.js. But if I open my dev tools "view page source" my changes are not actually in the HTML

This is also probably a good time to recommend documenting architecture decisions in the project. The project itself is very opinionated (which is great!), so all of that should be documented to help explain the reasons behind the decisions. I'd recommend reading these:

• http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions
• https://github.com/joelparkerhenderson/arc

There are a lot of moving parts to this setup and a sample app (say something like https://facebook.github.io/flux/docs/todo-list.html) would be really helpful.

We have a lot of comments that we added in when the repository was created.

In many cases, we should either write self-documenting code, as comments are at best, a necessary evil.

If we cannot change the function/variable names to be self-explanatory, we should consider extracting that into README.

@diegohaz - i noticed a couple of minor spelling errors on the main site:

Basic stack
It includes everything necessary to build a tipical web app with focus on productivity and developer experience.
Learn more about the recomended workflow

Should be typical, and recommended.

Just an FYI.

Thanks!

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?

"gl-react": "^4.0.1",
"gl-react-image": "^3.1.1",
"gl-react-instagramfilters": "^0.2.0",
"gl-react-native": "^4.0.1",

Latest version of gl-react and gl-react-native.

Expected behavior

Changing Surface style (height and width) should change sizes and rerender.

Actual behavior

Surface randomly disappears after changing the sizes.

Steps to reproduce the behavior

Type of issue

bug

My environment

n/a

Expected behavior

• to visit electrode-archetype-opt-stylus and understand how to use it

Current behavior

• current docs omit the critical how steps

Add native Expo Google API integration for login as a module next to WebBrowser implementation, e.g. auth/expo-google next to auth/google
Relevant docs:
https://docs.expo.io/versions/v31.0.0/sdk/google

When I click "live" on any of the links under https://router5.js.org/#examples

I see that router5 version is still 6, the redux example in particular still uses react-redux 5(current is 7)

npm ERR! code ELOCKVERIFY
npm ERR! Errors were found in your package-lock.json, run npm install to fix them.
npm ERR! Missing: expo@~37.0.3
npm ERR! Missing: react@~16.9.0
npm ERR! Missing: react-dom@~16.9.0
npm ERR! Missing: react-native@https://github.com/expo/react-native/archive/sdk-37.0.0.tar.gz
npm ERR! Missing: react-native-web@~0.11.7
npm ERR! Missing: babe

Once scrolling using ctrl + or control + mouse wheel there's no way of dragging the picture both with keyboard and mouse.
Double tap to zoom is missing

While this works great with the terminal example (it returns the desired HTML), I'm not sure how this can be implemented on, say a basic express app, where I want the crawlers to get the prerendered HTML for SEO purposes. One or two examples as to how to implement this would be awesome!

Other than that the project seems great!