<?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>topic Can you use `npx nebula serve` with Qlik Sense Desktop? in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Can-you-use-npx-nebula-serve-with-Qlik-Sense-Desktop/m-p/2544113#M109636</link>
    <description>&lt;P&gt;I'm getting `Failed to fetch csrf-token TypeError: Failed to fetch` because it provides no discernible config that has any affect on its ability to include the port when accessing the host.&lt;BR /&gt;${host} will always be &lt;SPAN&gt;"&lt;A href="https://localhost" target="_blank" rel="noopener"&gt;https://localhost&lt;/A&gt;"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;// getCsrfToken.js
export default async function getCsrfToken(host) {
try {
const res = await fetch(`${host}/qps/csrftoken`, { credentials: 'include' });
const token = res.headers.get('QLIK-CSRF-TOKEN');
if (token) {
return token;
}
return '';
} catch (err) {
console.log('Failed to fetch csrf-token', err);
}
return '';
}&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;I've tried various flag and nebula.config.js like this&lt;/P&gt;&lt;LI-CODE lang="python"&gt;"start": "nebula serve --type serve --enigma.host localhost --enigma.port 4848"&lt;/LI-CODE&gt;</description>
    <pubDate>Tue, 03 Mar 2026 17:34:52 GMT</pubDate>
    <dc:creator>JoelStransky</dc:creator>
    <dc:date>2026-03-03T17:34:52Z</dc:date>
    <item>
      <title>Can you use `npx nebula serve` with Qlik Sense Desktop?</title>
      <link>https://community.qlik.com/t5/App-Development/Can-you-use-npx-nebula-serve-with-Qlik-Sense-Desktop/m-p/2544113#M109636</link>
      <description>&lt;P&gt;I'm getting `Failed to fetch csrf-token TypeError: Failed to fetch` because it provides no discernible config that has any affect on its ability to include the port when accessing the host.&lt;BR /&gt;${host} will always be &lt;SPAN&gt;"&lt;A href="https://localhost" target="_blank" rel="noopener"&gt;https://localhost&lt;/A&gt;"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;// getCsrfToken.js
export default async function getCsrfToken(host) {
try {
const res = await fetch(`${host}/qps/csrftoken`, { credentials: 'include' });
const token = res.headers.get('QLIK-CSRF-TOKEN');
if (token) {
return token;
}
return '';
} catch (err) {
console.log('Failed to fetch csrf-token', err);
}
return '';
}&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;I've tried various flag and nebula.config.js like this&lt;/P&gt;&lt;LI-CODE lang="python"&gt;"start": "nebula serve --type serve --enigma.host localhost --enigma.port 4848"&lt;/LI-CODE&gt;</description>
      <pubDate>Tue, 03 Mar 2026 17:34:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Can-you-use-npx-nebula-serve-with-Qlik-Sense-Desktop/m-p/2544113#M109636</guid>
      <dc:creator>JoelStransky</dc:creator>
      <dc:date>2026-03-03T17:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: Can you use `npx nebula serve` with Qlik Sense Desktop?</title>
      <link>https://community.qlik.com/t5/App-Development/Can-you-use-npx-nebula-serve-with-Qlik-Sense-Desktop/m-p/2547755#M110087</link>
      <description>&lt;P&gt;Have you tried this method from internet. It uses Nebula.js using Qlik sense Desktop.&lt;/P&gt;&lt;P&gt;&lt;A href="https://extendingqlik.upper88.com/qlik-nebula-js-first-test-drive/" target="_self"&gt;https://extendingqlik.upper88.com/qlik-nebula-js-first-test-drive/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 26 Apr 2026 12:15:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Can-you-use-npx-nebula-serve-with-Qlik-Sense-Desktop/m-p/2547755#M110087</guid>
      <dc:creator>vighnesh_gawad</dc:creator>
      <dc:date>2026-04-26T12:15:39Z</dc:date>
    </item>
  </channel>
</rss>

