archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/examples/custom-charset
History
Shu Uesugi 6804039e94 Make example READMEs more consistent (#10124) 
* npx create → npm init

* Fix inconsistent instructions

* Update amp-first

* Update with-graphql-react

* with-firebase-cloud-messaging

* Update with-higher-order-component

* change create-next-app url

* Update create-next-app instruction

* Update instructions to use npm instead of npx

* Move "the idea behind the example" to top

* Rename

* Rename

* Update contributing.md with a README template
2020-01-16 23:23:56 +01:00
..
pages Examples: stabalise README format and create-next-app usage (#4009) 2018-04-03 14:19:05 +02:00
package.json Test updater script on examples folder (#5993) 2019-01-05 12:19:27 +01:00
README.md Make example READMEs more consistent (#10124) 2020-01-16 23:23:56 +01:00
server.js Add prettier for examples directory (#5909) 2018-12-17 17:34:32 +01:00

README.md

Custom server example

The HTTP/1.1 specification says - if charset is not set in the http header then the browser defaults use ISO-8859-1. For languages like Polish, Albanian, Hungarian, Czech, Slovak, Slovene, there will be broken characters encoding from SSR.

You can overwrite Content-Type in getInitialProps. But if you want to handle it as a server side concern, you can use this as an simple example.

How to use

Using create-next-app

Execute create-next-app with npm or Yarn to bootstrap the example:

npm init next-app --example custom-charset custom-charset-app
# or
yarn create next-app --example custom-charset custom-charset-app

Download manually

Download the example:

curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/custom-charset
cd custom-charset

Install it and run:

npm install
npm run dev
# or
yarn
yarn dev

Deploy it to the cloud with now (download)

now