- 03 6月, 2020 13 次提交
-
-
由 Todor Totev 提交于
Related to [11014](https://github.com/vercel/next.js/issues/11014) 1. Moved the reducer into the store and created new store file 2. The example was using a server that was no longer available, now it uses JSON placeholder instead. 3. Moved from getInitialProps to getStaticProps 4. Refactored all the classes to functional components, using the new redux hooks API. 5. Upgraded all the packages and using custom redux wrapper instead of next-redux-wrapper, which I have removed from the example. 6. Upgraded all the other packages. Please, let me know if I should change anything.
-
由 Todor Totev 提交于
**First, apologies for a second PR on the same issue but I was working on this already so I thought I'd push it and let you decide which you want to merge.** The PR is related to [13466](https://github.com/vercel/next.js/issues/13466). Based on my research, the error happens if the options are empty, null, or undefined. That's why I have decided that the most proper check would be using the! post-fix expression operator may assert that its operand is non-null and non-undefined. ``if (options == null)`` (Optional) I have also added a warning, which warns the user if the passed "dev" variable is not a boolean. It's my first PR on the "packages" part of the repo so I'd be glad to receive all kinds of critics. If you want me to change or remove anything, I'm open to suggestions. --- Fixes #13466
-
由 Joe Haddad 提交于
`JAMstack` is now `Jamstack`.
-
由 Tyler Evans 提交于
Took me a while to figure out why the simple data fetching examples weren't working in my project, which I based off this template. Here's the fix.
-
由 Joe Haddad 提交于
-
由 Jefferson Bledsoe 提交于
The [docs for customising the PostCSS config](https://nextjs.org/docs/advanced-features/customizing-postcss-config) warn the user they will need to manually install any dependencies that Next.JS will implicitly use if the config is not overridden. `postcss-preset-env` is missing from the install command.
-
由 Tim Neutkens 提交于
Prepares for the upgrade to webpack 5
-
由 Joe Haddad 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Joe Haddad 提交于
-
由 Luis Alvarez D 提交于
This was a change that I forgot to push into the Agility CMS example PR, adding it now.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Removes some dangling references to non-existent experimental options.
-
由 Joe Haddad 提交于
This skips reading from the file system because the `sourcesContent` can be used to access the source code. I've completely removed the filesystem fallback, because it's probably not our code that'd be syntax highlighted anyway.
-
- 02 6月, 2020 18 次提交
-
-
由 Joe Haddad 提交于
This removes remaining references to `granularChunks` in configs, error messages, and comments. Also removed the `process.env.__NEXT_GRANULAR_CHUNKS` value. --- Follow up to: https://github.com/vercel/next.js/pull/13663
-
由 Tim Neutkens 提交于
The option was released a few months ago so we can get rid of this option.
-
由 Tim Neutkens 提交于
https://twitter.com/vercel/status/1267650234236252161 The variables for the launchEditor feature were kept consistent with Create React App so it's probably a good idea for them to change them too: https://github.com/facebook/create-react-app/search?q=WINDOWS_FILE_NAME_WHITELIST Prior discussions on this topic: - https://github.com/hashicorp/consul/issues/7901 - https://github.com/styled-system/styled-system/issues/391 - https://github.com/go-sql-driver/mysql/pull/1116 - https://github.com/lagom/lagom/issues/2532 - https://github.com/grafana/grafana/issues/18841
-
由 James Vidler 提交于
-
由 Kirill Konshin 提交于
Follow up for #11802 Makes sure app is not opted out of Automatic Static Optimization.
-
由 Shu Uesugi 提交于
* Strapi Example * Fix og image URL * Remove next.config.js * Apply updates * Remove API_URL * Bugfixes * Finish Strapi README * Deploy Strapi * Add strapi examples * now → vercel [ch1796] * Use npx * Minor readme update * Prettier fix Co-authored-by: NLuis Alvarez <luis@vercel.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
In serverless mode, it's best practice to propagate an unhandled error so that the function is disposed instead of recycled. This helps fix the "bad state" problem.
-
由 Joe Haddad 提交于
This feature is still experimental.
-
由 Luis Alvarez D 提交于
* Added most of the stuff * Updated pages * Removed unrequired deps * API fixes * Fixes fixes and updated readme * Updated og image * Added demo and links to example * Updated packages * update name. bump dependencies * Renamed .env.example to .env.local.example * Added node_modules to .gitignore * use recommended config * enable absolute import/alias support * remove jsconfig.json * allow HTML entities in post titles * add underline to content links * add basic ul & ol styles * add code block styles * add basic text alignment * add basic image alignment styles * adjust pre font-size and figcaption * indent ul,ol lists to line up with grid * add basic button styles * add basic file styles * add basic blockquote style * add basic audio styles * add h4 and enhance blockquote styles * add basic cover block styles * add basic verse styles * add basic two-column block styles * add tags * add categories * Only ignore .vercel The rest is injected by create-next-app * now → vercel * npm init → npx * Wordsmith * Wordsmith * Wordsmith * Wordsmith * Improve issue link * Wordsmith Co-authored-by: NGreg Rickaby <greg@gregrickaby.com> Co-authored-by: NJoe Haddad <joe.haddad@zeit.co> Co-authored-by: NShu Uesugi <shu@chibicode.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Tim Neutkens 提交于
Was going through _document and noticed some variable shadowing going on. Added a rule for it to our eslint configuration and went through all warnings with @Timer.
-
由 Rafael Almeida 提交于
The motivation for this PR is well explained here: https://github.com/facebook/create-react-app/pull/8177 I can expand it to the other examples too if you agree with the change
-
由 Tim Neutkens 提交于
Follow-up to #12218, missed this bit of code.
-
由 Shu Uesugi 提交于
This undoes https://github.com/vercel/next.js/pull/13138 as the rename is done.
-
由 Todor Totev 提交于
Closes #12664 Closes #13604 The culprit was not only changing the library directory, but also having the icons version past 4.0.6. Also, the components which used the library had to be adjusted according to the new changes. Confirmed that it works both in production and development. Confirmed that it builds on dev and production. ![Alt Text](https://media.giphy.com/media/dZ46aA1Rs7Oi1wSQKU/giphy.gif)
-
由 Joe Haddad 提交于
This updates old examples to the more universal `npx` command. Fixes https://github.com/vercel/next.js/discussions/12103
-
由 Akhila Ariyachandra 提交于
-
由 Jan Potoms 提交于
Fixes https://github.com/vercel/next.js/issues/13524 To do: - [x] fix dev mode - [x] there's a ~route ordering or~ trailing slash issue with top level catch-all (current tests reflect that) - [x] in this test `/get-static-paths/whatever` should fall back to `/[[...optionalName]].js` since `fallback` is `false` in its `getStaticPaths` method. ~Currently seems to 500~ must have been a glitch - [x] add tests for `null`, `undefined` ~and `false`~ behavior as well (if decided these are valid) - [x] ~add tests for string params as well~ this is not allowed for catch-all routes - [x] test behavior when fallback is enabled and a top level catch-all exists
-
- 01 6月, 2020 9 次提交
-
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This addresses some errors for `/_next/data` requests where encoded `/` values in dynamic route param would cause invalid behavior, a headers already sent error would be shown when sending the fallback page in development, and when rendering the `_error` page for a data request the error response would still be treated as a data request. This also adds test cases for these errors to prevent regression
-
由 Luis Alvarez D 提交于
- The first links were updated to match the new titles - Removed the `# .env.local` comment as it's redundant - Added links to the sections related to data fetching
-
由 Tim Neutkens 提交于
Based on feedback from @mcsdevv's team. Solves many of the issues users run into with the current docs.
-
由 Tim Neutkens 提交于
Since the reload function was removed this parameter is no longer needed
💯 -
由 Luis Alvarez D 提交于
Leftover from a past PR
-
由 Luis Alvarez D 提交于
Also added `.now`, this should make sure that if the Vercel CLI is used inside the examples to deploy a project, the project folder is not added to the list of changes.
-
由 Martin Bavio 提交于
This PR fixes https://github.com/vercel/next.js/issues/4883. It introduces a new global variable (`window.__REHYDRATE_IDS`) only when necessary. In the case of the `with-react-with-styles` example, rehydration isn't happening, so I removed the creation of the variable. In the case of the `with-react-intl` example, the information doesn't seem to be set anymore on `__NEXT_DATA__`, so I just removed the default reference to it.
-
由 Jan Potoms 提交于
Looks like `caniuse-lite` is out of date and causing test failures. - I upgraded both `browserslist` and `caniuse-lite` to latest semver compatible version. - This seemed to cause changes in ncc compiled files, so recompiled. - `lint-staged` failed on these files even though they should be ignored. As a fix, I applied the advice from https://github.com/okonet/lint-staged#how-can-i-ignore-files-from-eslintignore- - Updated some test snapshots.
🤔 not sure this is the way to go
-