From d9359b1a299148e0e18d9782465a4471951fae1b Mon Sep 17 00:00:00 2001
From: Tim <tim@unegma.com>
Date: Mon, 14 Dec 2020 18:42:54 +0000
Subject: [PATCH] Update zokrates_js.html

After speaking with @dark64, we realised that the import needs to be 'zokrates-js' not 'zokrates-js/node'.
I have also included a link to an article on using React with WASM which helps to solve the 'Module parse failed: magic header not detected' error
---
 toolbox/zokrates_js.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/toolbox/zokrates_js.html b/toolbox/zokrates_js.html
index 6c2e2ff..57f3221 100644
--- a/toolbox/zokrates_js.html
+++ b/toolbox/zokrates_js.html
@@ -145,10 +145,11 @@ <h1 class="menu-title">ZoKrates</h1>
 <p><strong>Note:</strong> As this library uses a model where the wasm module itself is natively an ES module, you will need a bundler of some form.
 Currently the only known bundler known to be fully compatible with <code>zokrates-js</code> is <a href="https://webpack.js.org/">Webpack</a>.
 The choice of this default was done to reflect the trends of the JS ecosystem.</p>
+<p>If using the library with React, it may be helpful to <a href="https://www.telerik.com/blogs/using-webassembly-with-react">reference this post</a> on using WASM with React.</p>                        
 <pre><code class="language-js">import { initialize } from 'zokrates-js';
 </code></pre>
 <a class="header" href="#node" id="node"><h5>Node</h5></a>
-<pre><code class="language-js">const { initialize } = require('zokrates-js/node');
+<pre><code class="language-js">const { initialize } = require('zokrates-js');
 </code></pre>
 <a class="header" href="#example" id="example"><h2>Example</h2></a>
 <pre><code class="language-js">initialize().then((zokratesProvider) =&gt; {