Next.js emotion cannot start development

[yudyananda]

I'm using next.js and emotion, start with the example but cannot start the development (with or without webpack5)

Here's what my console show to me (without any config)

error - ./node_modules/path-type/index.js:3:0
Module not found: Can't resolve 'fs'
null

with config

// next.config.js
module.exports = {
  // future: { webpack5: true } not required anymore 
  // https://nextjs.org/docs/messages/future-webpack5-moved-to-webpack5
  webpack: config => {
    // Unset client-side javascript that only works server-side
    config.resolve.fallback = { fs: false, module: false }

    return config
  },
}

// console error
error - ./node_modules/import-fresh/index.js:2:0
Module not found: Can't resolve 'path'
null 

with config without webpack5

// next.config.js
module.exports = {
  webpack5: false,
  webpack: (config, { isServer }) => {
    if (!isServer) {
      // Unset client-side javascript that only works server-side
      // https://github.com/vercel/next.js/issues/7755#issuecomment-508633125
      config.node = { fs: 'empty', module: 'empty' }
    }

    return config
  },
}


// console error
warn  - ./node_modules/twin.macro/node_modules/babel-plugin-macros/dist/index.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

./node_modules/twin.macro/macro.js
Critical dependency: the request of a dependency is an expression

are there any changes not covered by the documentation?

[ben-rogerson]

Hey there, next has made some improvements lately and no longer requires this custom next.config fix:

config.node = { fs: 'empty', module: 'empty' }

I've just updated the example to remove the fix - could you try again?