<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Built-in support for unspecified es modules in ArcGIS Experience Builder Ideas</title>
    <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/built-in-support-for-unspecified-es-modules/idi-p/1337135</link>
    <description>&lt;P&gt;Custom Widgets are not currently able to use es modules that are not fully specified without adding custom webpack configuration in the webpack overrides file.&amp;nbsp; This works for local development but makes distribution of custom widgets difficult. Every instance of developer edition that uses the custom widget requires that the widget-webpack-overrides.js file be changed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the webpack overrides could be done by each widget individually, or if the default webpack config included the snippet below then npm modules marked with `type: module` in their package.json would be easily usable in custom widgets&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;module: {
  rules: [
    ...,
    {
      test: /\.m?js/,
      resolve: {
        fullySpecified: false
      }
    }
  ]
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Oct 2023 21:46:13 GMT</pubDate>
    <dc:creator>MichaelKowal</dc:creator>
    <dc:date>2023-10-11T21:46:13Z</dc:date>
    <item>
      <title>Built-in support for unspecified es modules</title>
      <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/built-in-support-for-unspecified-es-modules/idi-p/1337135</link>
      <description>&lt;P&gt;Custom Widgets are not currently able to use es modules that are not fully specified without adding custom webpack configuration in the webpack overrides file.&amp;nbsp; This works for local development but makes distribution of custom widgets difficult. Every instance of developer edition that uses the custom widget requires that the widget-webpack-overrides.js file be changed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the webpack overrides could be done by each widget individually, or if the default webpack config included the snippet below then npm modules marked with `type: module` in their package.json would be easily usable in custom widgets&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;module: {
  rules: [
    ...,
    {
      test: /\.m?js/,
      resolve: {
        fullySpecified: false
      }
    }
  ]
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Oct 2023 21:46:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-experience-builder-ideas/built-in-support-for-unspecified-es-modules/idi-p/1337135</guid>
      <dc:creator>MichaelKowal</dc:creator>
      <dc:date>2023-10-11T21:46:13Z</dc:date>
    </item>
  </channel>
</rss>

