next.js

2938 commits 5 branches 325 tags 42 MiB

Author	SHA1	Message	Date
Juan Olvera	7e12997af6	Test updater script on examples folder (#5993 ) I wrote a [script](https://github.com/j0lv3r4/dependency-version-updater) to update dependencies recursively in `package.json` files, e.g.: ``` $ node index.js --path="./examples" --dependencies="react=^16.7.0,react-dom=^16.7.0" ``` This PR contains the result against the examples folder.	2019-01-05 12:19:27 +01:00
Rafael Mariano	75efa817c0	Modify with-universal-configuration example (#4498 ) (#5948 ) Explains in details how the "with-universal-configuration" example works and rename it to "with-universal-configuration-build-time". Changing the example name makes the purpose of the example clear. The "env-config.js" file introduce one more sample of variable usage that instantiates an immediate value of the local environment variable. This makes it even clearer how build-time variable configuration works. The "index.js" page makes explicit the use of these configured environment variables. The universal configuration confusion happens when the value of the environment variable is used directly in the application causing an effect in server-side but not on the client side.	2018-12-26 20:19:31 +01:00

Author

SHA1

Message

Date

Juan Olvera

7e12997af6

Test updater script on examples folder (#5993 )

I wrote a [script](https://github.com/j0lv3r4/dependency-version-updater) to update dependencies recursively in `package.json` files, e.g.:

```
$ node index.js --path="./examples" --dependencies="react=^16.7.0,react-dom=^16.7.0"
```

This PR contains the result against the examples folder.

2019-01-05 12:19:27 +01:00

Rafael Mariano

75efa817c0

Modify with-universal-configuration example (#4498 ) (#5948 )

Explains in details how the "with-universal-configuration" example works and rename it to "with-universal-configuration-build-time". Changing the example name makes the purpose of the example clear.

The "env-config.js" file introduce one more sample of variable usage that instantiates an immediate value of the local environment variable. This makes it even clearer how build-time variable configuration works. The "index.js" page makes explicit the use of these configured environment variables.

The universal configuration confusion happens when the value of the environment variable is used directly in the application causing an effect in server-side but not on the client side.

2018-12-26 20:19:31 +01:00

Renamed from examples/with-universal-configuration/package.json (Browse further)

2 commits