Build never exist after upgrading to canary.35 or 8.1.0

After upgrading from 8.0.5-canary.34 to 35 or 8.1.0, build will never exit. It does build, so if I will exit manually and export or start, everything works, but the issue is, after project was built and all pages are listed in cli, build doesn’t exit automatically.

Can’t provide code to replicate, because having this issue on production project that I can’t share, any other projects work perfectly fine with 8.1.0.

Expected behavior:

• exit script after build completed

package.json

    "@material-ui/core": "^3.9.3",
    "formik": "^1.5.0",
    "next-redux-wrapper": "^1.3.5",
    "next": "8.0.5-canary.34",
    "react": "^16.8.6",
    "react-dom": "^16.8.6",
    "redux": "^4.0.0",
    "react-redux": "^5.1.0",
    "@babel/cli": "^7.4.3",
    "@babel/core": "^7.4.3",
    "@babel/node": "^7.2.2",
    "@babel/plugin-proposal-export-default-from": "^7.2.0",
    "@babel/preset-flow": "^7.0.0",

next.config.js

const defaultConfig = require('./config/default.json');
const stagingConfig = require('./config/staging.json');
const productionConfig = require('./config/production.json');

const { NODE_ENV } = process.env;
const extendConfig = NODE_ENV === 'production' ? productionConfig : NODE_ENV === 'staging' ? stagingConfig : {};

module.exports = {
  pageExtensions: ['jsx'],
  crossOrigin: 'anonymous',
  assetPrefix: extendConfig.CDN || '',
  generateBuildId: () => {
    const { version } = require('./package.json');
    return version;
  },
  env: {
    ...defaultConfig,
    ...extendConfig,
  },
};

.babelrc.js

module.exports = {
  presets: [
    '@babel/preset-flow',
    'next/babel',
  ],
  plugins: [
    ['import', { libraryName: 'antd' }],
    '@babel/plugin-proposal-export-default-from',
    'add-module-exports',
  ],
};

[sarkistlt]

@chuyik @timneutkens actually after updating to 8.1.1-canary.10 issue is fixed

[kachkaev]

Similar issue here. yarn build fails after version 8.0.5-canary.35 (works for 8.0.5-canary.34). What happens with 8.0.5-canary.35, 8.1.0 and 8.1.1-canary.0 is that a code in one of my app’s TS files ends up being executed. It exits with non-zero, because a required env variable is missing. This may be to do with some AMP stuff, but I’m not sure.

For next@8.1.1-canary.1 through next@8.1.1-canary.4 the build script works again. Starting next@8.1.1-canary.5, I see a TypeScript error, which follows Compiled successfully and the list of pages. This can be to do with ongoing work to deprecate @types/next and @zeit/next-typescript.