Alteryx UI SDK: Not able to launch Dev Harness

[chrisha]

Hey devs,

I'm using my free weekend to explore the new Platform SDK, which really looks promising. With no experience in React or TypeScript I see some learning ahed of me.

Unfortunately, I'm not able to get the dev harness running to quickly see if my interface works as intended.

I have followed the Quickstart Guide: https://help.alteryx.com/current/developer-help/platform-sdk-quickstart-guide

When I want to preview the tool, I get:

❯ npm run start

> dev-harness@1.0.0 start
> webpack-dev-server --open --config webpack.dev.js

sh: webpack-dev-server: command not found

As a first guess I assume that not all node modules have been properly installed. The UI SDK's documentation makes references to several installations that should be made, so I've tried:

❯ npm install
npm ERR! code ENOTFOUND
npm ERR! syscall getaddrinfo
npm ERR! errno ENOTFOUND
npm ERR! network request to https://artifactory.alteryx.com/artifactory/api/npm/npm/yargs/-/yargs-13.3.2.tgz failed, reason: getaddrinfo ENOTFOUND artifactory.alteryx.com
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

 I am not behind a proxy and my internet connection works well, but it seems https://artifactory.alteryx.com is not a public URL?

Does anyone have any guidance how to proceed?

Best

Christopher

[SeanAdams]

the only thing I can suggest @chrisha is that you make sure you're in the folder that has teh webpack.dev.js file in it.    On my dev folder, I created a venv to play with the new SDK, so this folder is venv\ui\DirectoryCreator\

May be worth re-running the two creators:

ayx_plugin_cli sdk-workspace-init

ayx_plugin_cli create-ayx-plugin

[chrisha]

Hi @SeanAdams , thanks for chiming in. The problem was a fixed URL in packages-lock.json that directed to an internal Alteryx URL. I have reported the issue on GitHub and it seems it is now fixed for any future setup: https://github.com/alteryx/dev-harness/issues/6#event-4801275055