"We are very forgiving of other humans making mistakes but have extremely little patience for computers making mistakes." "Chatbots were big in 2017 and it was right in terms of what people wanted, but the underlying technology wasn't there."ģ) We need to be careful with consumer-facing applications. "Natural language allows us to convey very complex concepts and ChatGPT gives us the ability to communicate in very complex ways directly with machines." Here are my top 10 takeaways:ġ) The interface is just as important as the underlying technology. Unless I'm missing something.I just listened to Open AI CEO Sam Altman talk for 45 minutes about ChatGPT and the future of AI this afternoon in San Francisco. ![]() I'm feeling that issue lies in storybook land as it seems to be only one proper way is to bump emotion version in storybook packages to fix those type conflicts. Theme is works in this minimal reproduction but for some reason it's not working in real codebase. Vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:23114 Uncaught TypeError: Cannot read properties of undefined (reading 'content')Īt theming_dist_ (vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:23114)Īt emotion_serialize_browser_esm_handleInterpolation (vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:43921)Īt serializeStyles (vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:44046)Īt vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:44214Īt vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:43586Īt renderWithHooks (vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:100945)Īt updateForwardRef (vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:103004)Īt beginWork (vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:105058)Īt HTMLUnknownElement.callCallback (vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:89905)Īt Object.invokeGuardedCallbackDev (vendors-node_modules_storybook_addon-actions_dist_esm_register_js-node_modules_storybook_:89954) ![]() (my idea was to convert css?: InterpolationWithTheme to css?: any, and it does work when editing directly, but I couldn't override it properly) I believe a proper fix could be done (with d.ts types or something) but couldn't figure it out. Surprisingly, they don't break the build, and my plan is to ts-ignore them manually (there are less than a dozen in NRN). Note that my setup works (compiles, both localhost and on Github actions) and can export a static version successfully, although there are a few TS errors because Next Right Now uses Emotion v11 while Storybook uses Emotion v10 and there are some type clashing. (My Next.js use Babel automatic mode, while SB Babel uses classic mode) ![]() It's important to split the Next.js babel config from Storybook babel config. JSX pragma requires /* jsx */ per file and is a bad way to solve this issue for end-users.īabel with automatic mode isn't compatible with MDX and will break part of Storybook.īabel with classic mode is the only correct way to configure babel.Ĭreating a. The underlying issue is due to Emotion 11 webpack configuration, which can use a Babel setup in either classic or automatic modes, or JSX pragma. Next Right Now uses Emotion 11, while its associated Storybook uses Emotion 10, this complicates things. I successfully managed to do this in the Next Right Now boilerplate, at UnlyEd/next-right-now#251 (I wasn't aware of this issue until now).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |