- 02 3月, 2019 2 次提交
-
-
由 Tim Neutkens 提交于
-
由 Anton Egorov 提交于
Fixes #6481
-
- 01 3月, 2019 8 次提交
-
-
由 Tim Neutkens 提交于
* await config * update config-promise-error test * Actually update test
-
由 Joe Haddad 提交于
This is a simple Babel plugin that overwrites certain attributes for `amp-` elements.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 tangye 提交于
* make router UrlIsNew comparing method work as expected * Remove shallow-equals from router and update urlIsNew check * Remove shallow-equals test since it is no longer used * Add integration test for asPath query
-
由 JJ Kasper 提交于
* Move next-bundle-analyzer to Next.js repo * Remove options from bundle-analyzer
-
由 Joe Haddad 提交于
* refactor(on-demand-entries): extract method: setupPing * Setup ping for amp pages * Missed a call
-
由 Joe Haddad 提交于
* refactor(on-demand-entries): extract method: setupPing * Missed a call
-
- 28 2月, 2019 4 次提交
-
-
由 JJ Kasper 提交于
* Fix dynamic require breaking after updating to v8 * Add test for dynamic require
-
由 JJ Kasper 提交于
After discussion, it was decided we should throw an error when a promise is returned in `next.config.js` as this isn't supported Fixes: #6416
-
由 JJ Kasper 提交于
After discussion added global styles to experimental-amp example
-
由 JJ Kasper 提交于
Fixes: https://github.com/zeit/now-builders/issues/160
-
- 27 2月, 2019 12 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
ncc unistore to fix install warning
-
由 Tim Neutkens 提交于
-
由 Kiko Beats 提交于
Hello, I have been using next.js for a while in a bunch of projects, so first for all thanks for all the vibrant effort around the project
🖤 . Always I see the server side next.js approach as an advantage, but also a weakness for the extra resources you need to have, specially comparing how cheap is a client side app. In order to do my things cheaper, I started using the SSR pattern you suggested in your examples, so useful! It saves time and resources. However, it was *too simple*. In a real production scenario, you need a bit more, specially related with send the right response headers to keep the rest of external network agent updated of your cache state. I started a tiny script code for doing that; basically, I copy/paste it on my ssr projects. Now, after a time, I think it's worth it publish it as [cacheable-response](https://github.com/Kikobeats/cacheable-response) module. The PR is for adding the module leverage into the next.js ssr example. It's doing the same, plus: - be possible use a multi storage cache (memory by default; mongodb, redis, mysql, supported). - sending `cache-control` response headers. - sending `X-Cache-Expired-At`, just a humanize way to see the expiration time. - support for forcing invalidation via `force=true` query parameter. I hope you like it🙂 -
由 Samundra Shrestha 提交于
* add extra info to authentication * Update auth.js
-
由 Luc 提交于
The latest version of babel-jest doesn't require `babel-core` with the bridge version anymore (updated in this PR : https://github.com/facebook/jest/pull/7016). So I'm updating with-jest and with-jest-react-testing-library examples accordingly.
-
由 Peter Kellner 提交于
* This is a non-working example of using PHASE_DEVELOPMENT_SERVER and PHASE_PRODUCTION_SERVER in production. I followed @timneutkens gist but was unable to make it work so I've boiled it down into this non-working example which I believe is the same. The README is not updated. Once it is figured out why this is not working, I'll clean up the project and update the pull request to be complete but for now just want to make it work. * added .eslintrc so that ` eslint . --fix` would work (not sure if that was really necessary). I assume that is same as `yarn lint-fix`. * fixes for standard style * fixes for standard style * Fix example and add some comments * Updated documentation and small change to logic of prod,dev,staging to work as expected. Added significantly more doc then I normally would in the hopes that it helps someone avoid the mis-understanding I went through. If it's too much, LMK and I'll reduce. * removed eslint and updated package.json to get rid of eslint and standardjs
-
由 JJ Kasper 提交于
After discussion it was decided instead of rewriting `next/config` and `next/head` imports to `next-server/config` and `next-server/head` we should just allow importing them as `next/config` and `next/head` Fixes: #6187
-
由 laiso 提交于
I'm working on examples/with-graphql-react changes to: - Next v7 to v8.0 and update dependencies - fix some errors for the change of graphql-react API
-
由 Connor Davis 提交于
-
由 Connor Davis 提交于
-
由 Connor Davis 提交于
-
- 26 2月, 2019 6 次提交
-
-
由 Matsumoto Toshi 提交于
* update next-preact * Update package.json
-
由 Jan Potoms 提交于
* Add failing test Test case for https://github.com/zeit/next.js/issues/6285 and https://github.com/zeit/next.js/issues/6380 * WIP * refactor and fix test * not problem * refactor back * rename variables like https://github.com/zeit/next.js/blob/canary/packages/next/server/on-demand-entry-handler.js#L163 * Update usage and add comment
-
由 JJ Kasper 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
* AMP page reload * Fix comment * Skip dev files in production * Polyfill event source * Add HMR test for AMP * Use webdriver * Use a dynamic server for HMR test * ffs
-
- 25 2月, 2019 3 次提交
-
-
由 HelloRusk 提交于
with-aphrodite example link didn't work properly
-
由 Jesse Hoffman 提交于
Next.js no longer uses `jsonPageRes`. This PR removes it from `en-us` and `zh-cn` documentation (formatting picked up some changes on zh-cn readme). Also updated the Flow type def for `getInitialProps`. Resolves #6363
-
由 Connor Davis 提交于
We don't use a lot of the features of `glob`, so let's remove it in favor of a leaner approach using regex. It's failing on windows and I have no idea why and don't own a windows machine
🤦 🏼 ♂️ (Ignore some of the commits in here, I forgot to create the new branch before I started working)
-
- 24 2月, 2019 1 次提交
-
-
由 Jepser Bernardino 提交于
Since version 18 (released in January), Hapi's `request.url` returns the parsed URL, so `parse` is not needed. Ref: - https://hapijs.com/api#-requesturl - https://github.com/hapijs/hapi/pull/3822
-
- 23 2月, 2019 4 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Connor Davis 提交于
-