1. 18 12月, 2018 2 次提交
  2. 16 12月, 2018 1 次提交
    • D
      add --node-args option (#5858) · ebf217cb
      DevSide 提交于
      This message is from @timneutkens after making changes:
      - Convert executables to Typescript
      - Remove `minimist` in favor of `arg` 
      - Implement `--node-args` usage: `--node-args="--throw-deprecation"`
      - Adds tests for usage of the `next` cli
      ebf217cb
  3. 13 12月, 2018 1 次提交
  4. 11 12月, 2018 1 次提交
  5. 04 12月, 2018 1 次提交
  6. 02 12月, 2018 1 次提交
  7. 28 11月, 2018 1 次提交
  8. 24 11月, 2018 1 次提交
  9. 21 11月, 2018 1 次提交
  10. 19 11月, 2018 2 次提交
  11. 14 11月, 2018 1 次提交
  12. 09 11月, 2018 1 次提交
  13. 06 11月, 2018 1 次提交
  14. 03 11月, 2018 1 次提交
  15. 02 11月, 2018 1 次提交
  16. 01 11月, 2018 1 次提交
  17. 27 10月, 2018 1 次提交
  18. 20 10月, 2018 1 次提交
  19. 10 10月, 2018 1 次提交
  20. 08 10月, 2018 1 次提交
  21. 06 10月, 2018 2 次提交
  22. 02 10月, 2018 1 次提交
  23. 01 10月, 2018 2 次提交
  24. 29 9月, 2018 2 次提交
  25. 22 9月, 2018 1 次提交
  26. 04 9月, 2018 1 次提交
    • T
      Provide a way to copy files in exportPathMap (#5089) · a8a97b07
      Tim Neutkens 提交于
      Related #4659 
      
      Adds the possibility for users to copy files inside of `exportPathMap`. This allows for adding `robots.txt` `sitemap.xml` etc. another use case is for https://github.com/hanford/next-offline, currently it's manually reading the buildId in `exportPathMap`.
      
      To allow users to do this we'll introduce a new parameter holding an object with the following keys:
      
      - `dev` - `true` when `exportPathMap` is being called in development. `false` when running `next export`. In development `exportPathMap` is used to define routes and behavior like copying files is not required.
      - `dir` - Absolute path to the project directory
      - `outDir` - Absolute path to the `out` directory (configurable with `-o` or `--outdir`). When `dev` is `true` the value of `outDir` will be `null`.
      - `distDir` - Absolute path to the `.next` directory (configurable using the `distDir` config key)
      - `buildId` - The buildId the export is running for
      
      Example usage:
      
      ```js
      // next.config.js
      const fs = require('fs')
      const {join} = require('path')
      const {promisify} = require('util')
      const copyFile = promisify(fs.copyFile)
      
      module.exports = {
        exportPathMap: async function (defaultPathMap, {dev, dir, outDir, distDir, buildId}) {
          if(dev) {
            return defaultPathMap
          }
          // This will copy robots.txt from your project root into the out directory
          await copyFile(join(dir, 'robots.txt'), join(outDir, 'robots.txt'))
          return defaultPathMap
        }
      }
      ```
      a8a97b07
  27. 03 9月, 2018 1 次提交
  28. 22 8月, 2018 1 次提交
  29. 20 8月, 2018 1 次提交
  30. 18 8月, 2018 1 次提交
  31. 14 8月, 2018 2 次提交
  32. 26 7月, 2018 1 次提交
  33. 24 7月, 2018 2 次提交