<p dir="auto">When I run the latest master branch with docker-compose.yml, then I login as admin with password admin. But once I login, there is just a close button and I can see the following error in one of the container.</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="superset-node_1    |
superset-node_1    | &gt; superset@0.999.0-dev dev /app/superset/assets
superset-node_1    | &gt; webpack --mode=development --colors --progress --debug --watch
superset-node_1    |
superset-node_1    | sh: 1: webpack: not found
superset-node_1    | npm ERR! code ELIFECYCLE
superset-node_1    | npm ERR! syscall spawn
superset-node_1    | npm ERR! file sh
superset-node_1    | npm ERR! errno ENOENT
superset-node_1    | npm ERR! superset@0.999.0-dev dev: `webpack --mode=development --colors --progress --debug --watch`
superset-node_1    | npm ERR! spawn ENOENT
superset-node_1    | npm ERR!
superset-node_1    | npm ERR! Failed at the superset@0.999.0-dev dev script.
superset-node_1    | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
superset-node_1    |
superset-node_1    | npm ERR! A complete log of this run can be found in:
superset-node_1    | npm ERR!     /root/.npm/_logs/2019-12-23T02_34_06_505Z-debug.log
incubator-superset_superset-node_1 exited with code 1"><pre class="notranslate"><code class="notranslate">superset-node_1    |
superset-node_1    | &gt; superset@0.999.0-dev dev /app/superset/assets
superset-node_1    | &gt; webpack --mode=development --colors --progress --debug --watch
superset-node_1    |
superset-node_1    | sh: 1: webpack: not found
superset-node_1    | npm ERR! code ELIFECYCLE
superset-node_1    | npm ERR! syscall spawn
superset-node_1    | npm ERR! file sh
superset-node_1    | npm ERR! errno ENOENT
superset-node_1    | npm ERR! superset@0.999.0-dev dev: `webpack --mode=development --colors --progress --debug --watch`
superset-node_1    | npm ERR! spawn ENOENT
superset-node_1    | npm ERR!
superset-node_1    | npm ERR! Failed at the superset@0.999.0-dev dev script.
superset-node_1    | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
superset-node_1    |
superset-node_1    | npm ERR! A complete log of this run can be found in:
superset-node_1    | npm ERR!     /root/.npm/_logs/2019-12-23T02_34_06_505Z-debug.log
incubator-superset_superset-node_1 exited with code 1
</code></pre></div>
<h2 dir="auto">/root/.npm/_logs/2019-12-23T02_34_06_505Z-debug.log</h2>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'dev' ]
2 info using npm@6.13.4
3 info using node@v10.18.0
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle superset@0.999.0-dev~predev: superset@0.999.0-dev
6 info lifecycle superset@0.999.0-dev~dev: superset@0.999.0-dev
7 verbose lifecycle superset@0.999.0-dev~dev: unsafe-perm in lifecycle true
8 verbose lifecycle superset@0.999.0-dev~dev: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/app/superset/assets/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle superset@0.999.0-dev~dev: CWD: /app/superset/assets
10 silly lifecycle superset@0.999.0-dev~dev: Args: [ '-c',
10 silly lifecycle   'webpack --mode=development --colors --progress --debug --watch' ]
11 info lifecycle superset@0.999.0-dev~dev: Failed to exec dev script
12 verbose stack Error: superset@0.999.0-dev dev: `webpack --mode=development --colors --progress --debug --watch`
12 verbose stack spawn ENOENT
12 verbose stack     at ChildProcess.&lt;anonymous&gt; (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack     at ChildProcess.emit (events.js:198:13)
12 verbose stack     at maybeClose (internal/child_process.js:982:16)
12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
13 verbose pkgid superset@0.999.0-dev
14 verbose cwd /app/superset/assets
15 verbose Linux 4.9.184-linuxkit
16 verbose argv &quot;/usr/local/bin/node&quot; &quot;/usr/local/bin/npm&quot; &quot;run&quot; &quot;dev&quot;
17 verbose node v10.18.0
18 verbose npm  v6.13.4
19 error code ELIFECYCLE
20 error syscall spawn
21 error file sh
22 error errno ENOENT
23 error superset@0.999.0-dev dev: `webpack --mode=development --colors --progress --debug --watch`
23 error spawn ENOENT
24 error Failed at the superset@0.999.0-dev dev script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]"><pre class="notranslate"><code class="notranslate">0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'dev' ]
2 info using npm@6.13.4
3 info using node@v10.18.0
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle superset@0.999.0-dev~predev: superset@0.999.0-dev
6 info lifecycle superset@0.999.0-dev~dev: superset@0.999.0-dev
7 verbose lifecycle superset@0.999.0-dev~dev: unsafe-perm in lifecycle true
8 verbose lifecycle superset@0.999.0-dev~dev: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/app/superset/assets/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle superset@0.999.0-dev~dev: CWD: /app/superset/assets
10 silly lifecycle superset@0.999.0-dev~dev: Args: [ '-c',
10 silly lifecycle   'webpack --mode=development --colors --progress --debug --watch' ]
11 info lifecycle superset@0.999.0-dev~dev: Failed to exec dev script
12 verbose stack Error: superset@0.999.0-dev dev: `webpack --mode=development --colors --progress --debug --watch`
12 verbose stack spawn ENOENT
12 verbose stack     at ChildProcess.&lt;anonymous&gt; (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack     at ChildProcess.emit (events.js:198:13)
12 verbose stack     at maybeClose (internal/child_process.js:982:16)
12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
13 verbose pkgid superset@0.999.0-dev
14 verbose cwd /app/superset/assets
15 verbose Linux 4.9.184-linuxkit
16 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev"
17 verbose node v10.18.0
18 verbose npm  v6.13.4
19 error code ELIFECYCLE
20 error syscall spawn
21 error file sh
22 error errno ENOENT
23 error superset@0.999.0-dev dev: `webpack --mode=development --colors --progress --debug --watch`
23 error spawn ENOENT
24 error Failed at the superset@0.999.0-dev dev script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
</code></pre></div>
<p dir="auto">Reviewing the documentation and example PRs for how to add a new visualisation, I have followed those steps as closely as possible (apart from some folders which seem to have been moved). When adding the new visualiation to a dashboard, I get the following error:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="An error occurred while rendering the visualization: Error: Item with key &quot;custom_vis&quot; is not registered."><pre class="notranslate"><code class="notranslate">An error occurred while rendering the visualization: Error: Item with key "custom_vis" is not registered.
</code></pre></div>
<h3 dir="auto">Expected results</h3>
<p dir="auto">The visualisation loads</p>
<h3 dir="auto">Actual results</h3>
<p dir="auto">A yellow box displays with the error, along with the same message through console.warn.</p>
<h4 dir="auto">How to reproduce the bug</h4>
<p dir="auto">Follow the structure of <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="237412594" data-permission-text="Title is private" data-url="https://github.com/apache/superset/issues/3013" data-hovercard-type="pull_request" data-hovercard-url="/apache/superset/pull/3013/hovercard" href="https://github.com/apache/superset/pull/3013">#3013</a> in order to create a new visualisation, run <code class="notranslate">npm run build</code> and <code class="notranslate">npm run sync-backend</code>, start server. Add new chart using the visualisation, and add to dashboard. Visit dashboard.</p>
<h3 dir="auto">Environment</h3>
<ul dir="auto">
<li>superset version: <code class="notranslate">v0.29rc7</code></li>
<li>python version: <code class="notranslate">Python 3.7.3</code></li>
<li>node.js version: <code class="notranslate">v11.11.0</code></li>
<li>npm version: <code class="notranslate">6.7.0</code></li>
</ul>
<h3 dir="auto">Checklist</h3>
<p dir="auto">Make sure these boxes are checked before submitting your issue - thank you!</p>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have checked the superset logs for python stacktraces and included it here as text if there are any.</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> I have reproduced the issue with at least the latest released version of superset.</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have checked the issue tracker for the same issue and I haven't found one similar.</li>
</ul>