Results 1 to 2 of 2

Thread: ExtReactWebpackPlugin and publicpath

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User
    Join Date
    Aug 2015
    Posts
    2
    Vote Rating
    0
      0  

    Default ExtReactWebpackPlugin and publicpath

    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:
    Code:
    {
       ...
       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.

  2. #2
    Ext Team Member
    Join Date
    Sep 2017
    Posts
    885
    Vote Rating
    -455
      0  

    Default

    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



Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •