Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build process hang with ts 3.9 #13129

Closed
Innei opened this issue May 20, 2020 · 2 comments
Closed

build process hang with ts 3.9 #13129

Innei opened this issue May 20, 2020 · 2 comments
Labels
good first issue Easy to fix issues, good for newcomers

Comments

@Innei
Copy link

Innei commented May 20, 2020

Bug report

I upgrade typescript 3.8 to 3.9.x, and I run next build, but hang with the message. Creating an optimized production build .. After a long wait, but hang. No other hints.

Describe the bug

Can't build production with typescript 3.9.x, build process hang.

To Reproduce

I don't kwon how to reproduce, My node version is node v12.16.3, next version is 9.4.1, os mac 10.14.2

and this is my next.config.js

const isProd = process.env.NODE_ENV === 'production'
const withBundleAnalyzer = require('@next/bundle-analyzer')({
  enabled: process.env.ANALYZE === 'true',
})
const env = require('dotenv').config().parsed || {}
const withImages = require('next-images')
module.exports = withImages(
  withBundleAnalyzer({
    env: {
      PORT: 2323,
      ...env,
    },
    assetPrefix: isProd ? env.ASSETPREFIX || '' : '',
    experimental: {
      modern: true,
      async rewrites() {
        return [{ source: '/sitemap.xml', destination: '/api/sitemap' }]
      },
      catchAllRouting: true,
    },
  }),
)

Expected behavior

build success, not hang.

Screenshots

this is all output of the build process.

17:19:28 › yarn build                       
yarn run v1.22.4
$ cross-env NODE_ENV=production next build
info  - Loaded env from .env
warn  - You have enabled experimental feature(s).
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use them at your own risk.

> Using external babel configuration
> Location: "/Users/innei/GitHub/mx-web/.babelrc"
Creating an optimized production build ..

System information

My node version is node v12.16.3, next version is 9.4.1, os mac 10.15.2

@timneutkens timneutkens added good first issue Easy to fix issues, good for newcomers help wanted labels May 20, 2020
@Innei
Copy link
Author

Innei commented Jun 1, 2020

okay, it solved in the latest nextjs version.

@Innei Innei closed this as completed Jun 1, 2020
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Easy to fix issues, good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants