1. 16 Sep, 2018 7 commits
  2. 14 Sep, 2018 4 commits
  3. 12 Sep, 2018 6 commits
  4. 11 Sep, 2018 2 commits
  5. 10 Sep, 2018 1 commit
  6. 09 Sep, 2018 2 commits
  7. 08 Sep, 2018 1 commit
    • Tim Neutkens's avatar
      Set cwd on babel-loader (#5127) · d2160370
      Tim Neutkens authored
      Fixes #5125
      
      I'm not sure if this is a bug in babel-loader / babel-core or not. But this will at least temporary fix it till I hear back from @loganfsmyth 🙏
      d2160370
  8. 07 Sep, 2018 4 commits
    • Tim Neutkens's avatar
      7.0.0-canary.14 · fd67f22b
      Tim Neutkens authored
      fd67f22b
    • Tim Neutkens's avatar
      Make non-existent routes under `/_next` return 404 (#5120) · 8d304ed7
      Tim Neutkens authored
      Fixes #5114
      
      Also adds a test for it.
      8d304ed7
    • Evan Jacobs's avatar
      update hoist-non-react-statics (#5117) · 7c0de2c3
      Evan Jacobs authored
      you folks should really use semver ranges, but since greenkeeper
      is no longer running for this branch things have fallen behind
      
      in particular, there seems to be an incompatibility with multiple
      v2.x versions of this package in the same bundle as displayed here:
      
      styled-components/styled-components#1972
      
      When I force resolution to a particular h-n-r-s version, the issue
      goes away. This is true for both next 6 and next 7 canary.
      7c0de2c3
    • Julia Qiu's avatar
      Fix @babel/env modules config (#5119) · a9b1383b
      Julia Qiu authored
      Probably an oversight but currently env preset's `modules` option always evaluates to 'auto'. We probably want it to be set to false, especially in prod, to have Webpack handle modules natively.
      a9b1383b
  9. 06 Sep, 2018 2 commits
  10. 05 Sep, 2018 6 commits
  11. 04 Sep, 2018 5 commits
    • Diogo Dutra's avatar
      Fixed package.json (#4654) · 56937fd2
      Diogo Dutra authored
      Fix on relay script to proper ignore schema files
         added graphql as explict dependency
      56937fd2
    • Emmanuel Letallieur's avatar
      Fix custom-server-typescript not typechecking (#3954) · 82bdd432
      Emmanuel Letallieur authored
      Hi
      
      In the current version of the example __custom-server-typescript__, types are never checked.
      For instance, change the following line :
      ```
      const dev = process.env.NODE_ENV !== 'production'
      ```
      by :
      ```
      const dev: number = process.env.NODE_ENV !== 'production'
      ```
      then run `npm run dev`. The application launches perfectly, no error is thrown.
      
      In dev environnement, it is preferable to check types all the time, to get immediate feedback. This PR activates type checking. Only when using nodemon, so no impact on production.
      
      
      Now the above code will (rightfully) refuse to compile : 
      ```
      TSError: ⨯ Unable to compile TypeScript
      server/index.ts (6,7): Type 'boolean' is not assignable to type 'number'
      ```
      82bdd432
    • Tim Neutkens's avatar
      7.0.0-canary.12 · e7c41690
      Tim Neutkens authored
      e7c41690
    • Tim Neutkens's avatar
      Remove module.exports from client bundles (#5093) · d6c70508
      Tim Neutkens authored
      Removes `module.exports` so that `module` is no longer required
      
      Ref: https://github.com/zeit/next.js/pull/4943#discussion_r213232263
      
      This saves 15 bytes from every client bundle + 9 bytes from the initial HTML.
      d6c70508
    • Nathaniel Hill's avatar
      Fix HMR when parent directory starts with '.' (#4589) · 885eee80
      Nathaniel Hill authored
      @timneutkens 
      
      This simple change seems to work for me:
      
      ```
      const ignored = [
          '**/.*',
          'node_modules'
      ]
      ```
      
      I believe the regex is used here to try and work on windows as well. So, I wasted a bunch of time trying to figure out how to use a regex and/or the `path` module to ignore the parent directories until I noticed the following:
      
      > glob patterns are not filepaths. They are a type of regular language that is converted to a JavaScript regular expression. Thus, when forward slashes are defined in a glob pattern, the resulting regular expression will match windows or POSIX path separators just fine.
      
      this is from the [anymatch](https://github.com/micromatch/anymatch) documentation which is what webpack uses accoring to this:
      
      https://webpack.js.org/configuration/watch/#watchoptions-ignored
      
      I've verified this glob pattern solves the problem in my environment, can someone test and verify that this works on windows?
      
      👍 
      885eee80