...
You can serve your code to the Pulsar app via an HTTP server running on your development machine. One option is to use http-party/http-server to serve the contents of a directory, or if you are building a React or Angular app to run within Pulsar, these frameworks already have their own way to run an HTTP server.
NOTE: You must use relative paths for all resources you wish to serve from your development server-- this includes stylesheets, javascript files, images, and anything referenced in your code that does not exist inside of Pulsar. For example, use this: <script src='static/js/mycode.js' />
and not this: <script src='/static/js/mycode.js' />
Android Local Development Setup
...
Windows Local Development Setup
You Your local HTTP server must be running on your development machine
New in Pulsar version 12, you can connect to a local development server running on your Wifi – you aren’t restricted to just localhost (127.0.0.1) port 3002 like for Android development. Just type the appropriate ipaddr:port configuration into the configuration block on the Settings page.
NOTE that you can also still connect to a local development server running on localhost (127.0.0.1) port 3002. In this case you will also need to ensure that the Pulsar app has loopback exemption on your Windows machine:
Via a PowerShell or CMD shell prompt, run
CheckNetIsolation.exe LoopbackExempt -a -n="E3D1A000.PulsarforSalesforce_ta6n8xy84gcpg"
– You should only need to do this step once, per installation of Pulsar, per machine.Now verify that Pulsar is showing in the exemption list:
CheckNetIsolation.exe LoopbackExempt -s
iOS Local Development Setup
You Your local HTTP server must be running on your development machine
From the configuration block on the Settings Page, you must configure an ipaddr:port from the configuration block on the Settings Page
NOTE that if your development machine is a Mac with Apple silicon (not Intel) you can download Pulsar from the App Store and run and do all your testing there
Pulsar App Setup
Login to Pulsar and make sure your organization is fully synced at least once, including your Content Library documents.
From the Settings page, advanced section, toggle the development server on, and change the ipaddr:port as needed
If you do not see the toggle, then it is likely that your org is not configured correctly for development mode (for your specific username) – you might need to Refresh Settings if you just added your account to the developers list.
Note that once the development server toggle is on, it is sticky per-session. You will need to re-toggle it if you logout of the session and/or restart the Pulsar app.
...