1. 09 8月, 2019 1 次提交
  2. 03 8月, 2019 1 次提交
  3. 01 8月, 2019 1 次提交
  4. 31 7月, 2019 1 次提交
  5. 29 7月, 2019 1 次提交
  6. 28 7月, 2019 1 次提交
  7. 27 7月, 2019 3 次提交
  8. 26 7月, 2019 1 次提交
  9. 25 7月, 2019 2 次提交
  10. 24 7月, 2019 2 次提交
  11. 22 7月, 2019 2 次提交
  12. 18 7月, 2019 2 次提交
  13. 17 7月, 2019 1 次提交
  14. 16 7月, 2019 1 次提交
  15. 15 7月, 2019 2 次提交
  16. 13 7月, 2019 1 次提交
  17. 10 7月, 2019 3 次提交
  18. 09 7月, 2019 5 次提交
  19. 08 7月, 2019 1 次提交
  20. 03 7月, 2019 1 次提交
    • L
      Dynamic routing documentation (#7602) · c8bd4271
      Luis Fernando Alvarez D 提交于
      * Added basic example for dynamic routing
      
      * Added some basic docs for dynamic routing
      
      * Added more docs for dynamic routing
      
      * Used doctoc
      
      * fixed lint issues
      
      * Added useRouter to docs
      
      * Removed getInitialProps examples that are only using router props
      
      * Added useRouter to the navigation
      
      * Small fix
      
      * Updated to the latest dynamic routes implementation
      
      * lint fix
      
      * Update dynamic routing example
      
      * Tweak dynamic routing documentation
      
      * Make basic example basic again
      
      * Adjust dynamic routes section
      
      * Remove query param for dynamic routes example
      
      * Remove old note
      
      * Fix linting
      c8bd4271
  21. 02 7月, 2019 1 次提交
  22. 01 7月, 2019 1 次提交
  23. 29 6月, 2019 1 次提交
  24. 28 6月, 2019 2 次提交
  25. 27 6月, 2019 1 次提交
  26. 26 6月, 2019 1 次提交
    • E
      Updating hapijs package name (#7664) · 2259a7ec
      Eduardo P. Rivero 提交于
      * Updating hapijs package name
      
      Hapi was moved to a new module under the name @hapijs/hapi.
      
      Right now installing just as hapi is giving you this warning:
      
      ```bash
      npm WARN deprecated hapi@18.1.0: This module has moved and is now available at @hapi/hapi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
      ```
      This change does not affect the integration with next and it continues to work great.
      
      * Update package.json
      2259a7ec