publicRuntimeConfig is empty during development

[ghost]

Bug report

Using Next.js v9.0.3

Describe the bug

During development, the public runtime config is empty, even though publicRuntimeConfig is set in the config file.

However, the config is available when the project is built and running on production.

To Reproduce

1. Add publicRuntimeConfig in the next.config.js file.

// for example
publicRuntimeConfig: {
 API_URL: 'http://localhost:3001/api'
}

2. Open browser console and window.__NEXT_DATA__.runtimeConfig as shown in the image above.
3. It will return empty object {}, even though public runtime config should have API_URL value.

Expected behavior

publicRuntimeConfig should be available both in development and production.

System information

• Version of Next.js: 9.0.3

[ijjk]

Hi, I'm not able to reproduce this on 9.0.3 or the latest canary of Next.js (9.0.4-canary.3). Can you provide a link to a minimal repo with this issue. It's working with the below next.config.js and example page

// next.config.js
module.exports = {
  publicRuntimeConfig: {
    hello: 'world'
  }
}

// pages/index.js
import getConfig from 'next/config'
const { publicRuntimeConfig } = getConfig()

export default () => <p>hello {publicRuntimeConfig.hello}</p>

[ghost]

It is working now 😕 .
Thank you for the support.

[balazsorban44]

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.