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

Next.js chakraUI segmentation fault #1305

Closed
dominic-soh opened this issue Oct 9, 2022 · 1 comment
Closed

Next.js chakraUI segmentation fault #1305

dominic-soh opened this issue Oct 9, 2022 · 1 comment
Labels
bug Something isn't working ecosystem Something that relates to package or framework compatibility

Comments

@dominic-soh
Copy link

dominic-soh commented Oct 9, 2022

Version

0.1.13

Platform

Linux inshallah 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

What steps will reproduce the bug?

Install chakraUI according to documentation: https://chakra-ui.com/getting-started/nextjs-guide

Command:

$ bun add @chakra-ui/react @emotion/react@^11 @emotion/styled@^11 framer-motion@^6

Application root file: _app.tsx

import { ChakraProvider } from '@chakra-ui/react'
import "../styles/globals.css";

function MyApp({ Component, pageProps }) {
  return (
    <ChakraProvider>
      <Component {...pageProps} />
    </ChakraProvider>
  );
}

export default MyApp;

Start development server

$ bun dev

How often does it reproduce? Is there a required condition?

It will always result in segmentation fault after running bun dev

What is the expected behavior?

Runtime should not crash.

What do you see instead?

$ bun dev
[1.00ms] bun!! v0.1.13 (55bdf268)


  Link: http://localhost:3000


Possibly incompatible Next.js version:  12.2.3 . Please upgrade to Next.js 11.1.2 or Next.js 12.0.2+.

[54.26ms] Next.js ready! (powered by bun)
[70.49ms] / - 8 transpiled, 32 imports
[4.91ms] / - 4 transpiled, 18 imports
📜  File change: pages/_app.tsx
Error loading app: /home/dom/property-project/frontend/pages/_app
SyntaxError: Exported binding 'jsx' needs to refer to a top-level declared variable.
      at http://localhost:3000/blob:node_modules/@emotion/react/dist/emotion-react.worker.esm.js:305
SyntaxError: Exported binding 'jsx' needs to refer to a top-level declared variable.
      at http://localhost:3000/blob:node_modules/@emotion/react/dist/emotion-react.worker.esm.js:305

SegmentationFault at 0xE8FF6878DE050000


----- bun meta -----
Bun v0.1.13 (55bdf268) Linux x64 #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022
DevCommand: fast_refresh hot_module_reloading tsconfig filesystem_router framework macros public_folder bunfig 
Elapsed: 15744ms | User: 252ms | Sys: 64ms
RSS: 0.14GB | Peak: 0.14GB | Commit: 0.14GB | Faults: 0
----- bun meta -----

Ask for #help in https://bun.sh/discord or go to https://bun.sh/issues

Additional information

No response

@dominic-soh dominic-soh added bug Something isn't working needs repro Needs an example to reproduce labels Oct 9, 2022
@Electroid Electroid added ecosystem Something that relates to package or framework compatibility and removed needs repro Needs an example to reproduce labels Nov 3, 2022
@Electroid
Copy link
Contributor

bun dev was changed in Bun v1.0, it will now run the "dev" script in your package.json. Because of that, this issue is no longer applicable.

@Electroid Electroid closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ecosystem Something that relates to package or framework compatibility
Projects
None yet
Development

No branches or pull requests

2 participants