<?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 JavaScript API Interoperability with Other Loaders in ArcGIS JavaScript Maps SDK Ideas</title>
    <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-ideas/javascript-api-interoperability-with-other-loaders/idi-p/948793</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The&amp;nbsp;3.x and 4.x javascript api's and their&amp;nbsp;use of&amp;nbsp;dojo loader plugins lock&amp;nbsp;developers into using the dojo loader and the legacy dojo build system - or it places the&amp;nbsp;burden on the developer to create custom module loader implementations. I would like to see esri support the interoperability of module loading moving forward so developers can use modern loading/build/bundling tools with the 4.x api's without a lot of friction.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this idea is accepted, developers&amp;nbsp;cannot complain about&amp;nbsp;the implementation details of the javascript api leaking into their workflows/technology decisions.&amp;nbsp;The esri&amp;nbsp;technology decisions of the api will be an implementation detail instead of an influence.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 Mar 2017 18:59:44 GMT</pubDate>
    <dc:creator>stevegourley</dc:creator>
    <dc:date>2017-03-13T18:59:44Z</dc:date>
    <item>
      <title>JavaScript API Interoperability with Other Loaders</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-ideas/javascript-api-interoperability-with-other-loaders/idi-p/948793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The&amp;nbsp;3.x and 4.x javascript api's and their&amp;nbsp;use of&amp;nbsp;dojo loader plugins lock&amp;nbsp;developers into using the dojo loader and the legacy dojo build system - or it places the&amp;nbsp;burden on the developer to create custom module loader implementations. I would like to see esri support the interoperability of module loading moving forward so developers can use modern loading/build/bundling tools with the 4.x api's without a lot of friction.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this idea is accepted, developers&amp;nbsp;cannot complain about&amp;nbsp;the implementation details of the javascript api leaking into their workflows/technology decisions.&amp;nbsp;The esri&amp;nbsp;technology decisions of the api will be an implementation detail instead of an influence.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Mar 2017 18:59:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-ideas/javascript-api-interoperability-with-other-loaders/idi-p/948793</guid>
      <dc:creator>stevegourley</dc:creator>
      <dc:date>2017-03-13T18:59:44Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API Interoperability with Other Loaders - Status changed to: Implemented</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-ideas/javascript-api-interoperability-with-other-loaders/idc-p/1210817#M198</link>
      <description>&lt;P&gt;Late response - but I think the release of ES modules in 4.19 (and later improvements) covers this "idea".&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2022 15:47:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-ideas/javascript-api-interoperability-with-other-loaders/idc-p/1210817#M198</guid>
      <dc:creator>BjornSvensson</dc:creator>
      <dc:date>2022-09-08T15:47:10Z</dc:date>
    </item>
  </channel>
</rss>

