PDA

View Full Version : ExtReactWebpackPlugin and publicpath



Eugene.Nor
14 Mar 2019, 11:13 AM
It looks like ExtReactWebpackPlugin v 6.7.0 doesn't respect webpack output.publicPath config.
Worked fine in ExtReact v 6.5.3.

For instance,
Given webpack config:

{
...
output: {
...
publicPath: '/media/webpack/',
}
}
Generated ext.js and ext.css are injected to the page as ext-react/ext.js and ext-react/ext.css, when other chunks get /media/webpack/ prepended to their src in script tags

Is there a way to solve this or is it a bug?
Thanks.

Forum_Adm
14 Mar 2019, 7:22 PM
Thank you so much for your post. I apologize for the delay. I have shared this with the support staff to look into at their earliest convenience. Your patience is greatly appreciated! We do suggest using the support portal when you need assistance with a capability of a Sencha product, you have identified a situation where a products behavior is inconsistent with the product documentation and might indicate a software bug, or when the communication between you and Sencha needs to be private.

Thanks again,

Michele

mgusmano
19 Mar 2019, 6:39 AM
it looks like a bug - we will investigate


It looks like ExtReactWebpackPlugin v 6.7.0 doesn't respect webpack output.publicPath config.
Worked fine in ExtReact v 6.5.3.

For instance,
Given webpack config:

{
...
output: {
...
publicPath: '/media/webpack/',
}
}
Generated ext.js and ext.css are injected to the page as ext-react/ext.js and ext-react/ext.css, when other chunks get /media/webpack/ prepended to their src in script tags

Is there a way to solve this or is it a bug?
Thanks.

rakumar
16 Apr 2019, 12:13 PM
Hello Eugene,

This issue has been registered in our bug tracker for resolution, the reference Jira EXTREACT-37 will be linked here to track the status of the issue.

Regards,
Kumar
Sencha Support.