You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/06/16 13:02:00 UTC

[jira] [Commented] (DISPATCH-2339) Update console to React 18 and react-scripts 5

    [ https://issues.apache.org/jira/browse/DISPATCH-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555075#comment-17555075 ] 

ASF GitHub Bot commented on DISPATCH-2339:
------------------------------------------

jiridanek commented on PR #1560:
URL: https://github.com/apache/qpid-dispatch/pull/1560#issuecomment-1157633726

   I wanted to wait for rhea release that would incorporate valerio's fix that makes CRACO (or other such workaround) unnecessary. But maybe best not to wait.




> Update console to React 18 and react-scripts 5
> ----------------------------------------------
>
>                 Key: DISPATCH-2339
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-2339
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Console
>    Affects Versions: 1.19.0
>            Reporter: Jiri Daněk
>            Priority: Major
>             Fix For: 1.20.0
>
>
> {noformat}
> $ npx react-scripts start
> (node:836641) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:836641) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: 'onBeforeSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
> Starting the development server...
> Failed to compile.
> Module not found: Error: Can't resolve 'os' in '/home/jdanek/repos/qpid/qpid-dispatch/console/react/node_modules/rhea/lib'
> BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
> This is no longer the case. Verify if you need this module and configure a polyfill for it.
> If you want to include a polyfill, you need to:
>         - add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
>         - install 'os-browserify'
> If you don't want to include a polyfill, you can use an empty module like this:
>         resolve.fallback: { "os": false }
> ERROR in ./node_modules/rhea/lib/connection.js 36:9-22
> Module not found: Error: Can't resolve 'os' in '/home/jdanek/repos/qpid/qpid-dispatch/console/react/node_modules/rhea/lib'
> BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
> This is no longer the case. Verify if you need this module and configure a polyfill for it.
> If you want to include a polyfill, you need to:
>         - add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
>         - install 'os-browserify'
> If you don't want to include a polyfill, you can use an empty module like this:
>         resolve.fallback: { "os": false }
> ERROR in ./node_modules/rhea/lib/connection.js 38:11-26
> Module not found: Error: Can't resolve 'path' in '/home/jdanek/repos/qpid/qpid-dispatch/console/react/node_modules/rhea/lib'
> BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
> This is no longer the case. Verify if you need this module and configure a polyfill for it.
> If you want to include a polyfill, you need to:
>         - add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
>         - install 'path-browserify'
> If you don't want to include a polyfill, you can use an empty module like this:
>         resolve.fallback: { "path": false }
> webpack compiled with 2 errors
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org