[PathKit] Remove experimental- from package names

On the demo page, we use the skia-cdn bucket to hopefully
have better performance than unpkg.

Additionally, on the demo page, we default to using the
WASM version if supported by the browser.

Docs-Preview: https://skia.org/?cl=150904
Bug: skia:8216
Change-Id: I901016e95b8d66803053680691aac4d314821d18
Reviewed-on: https://skia-review.googlesource.com/150904
Reviewed-by: Joe Gregorio <jcgregorio@google.com>
diff --git a/modules/pathkit/npm-asmjs/README.md b/modules/pathkit/npm-asmjs/README.md
index e8bcf2f..a04007f 100644
--- a/modules/pathkit/npm-asmjs/README.md
+++ b/modules/pathkit/npm-asmjs/README.md
@@ -1,10 +1,10 @@
 An asm.js version of Skia's PathOps toolkit.
 
-To use the library, run `npm install experimental-pathkit-asmjs` and then simply include it:
+To use the library, run `npm install pathkit-asmjs` and then simply include it:
 
-    <script src="/node_modules/experimental-pathkit-asmjs/bin/pathkit.js"></script>
+    <script src="/node_modules/pathkit-asmjs/bin/pathkit.js"></script>
     PathKitInit({
-        locateFile: (file) => '/node_modules/experimental-pathkit-asmjs/bin/'+file,
+        locateFile: (file) => '/node_modules/pathkit-asmjs/bin/'+file,
     }).then((PathKit) => {
         // Code goes here using PathKit
     });
@@ -28,7 +28,7 @@
 
 In the JS code, use require():
 
-    const PathKitInit = require('experimental-pathkit-asmjs/bin/pathkit.js')
+    const PathKitInit = require('pathkit-asmjs/bin/pathkit.js')
     PathKitInit().then((PathKit) => {
         // Code goes here using PathKit
     })
@@ -40,13 +40,13 @@
 
     config.plugins.push(
         new CopyWebpackPlugin([
-            { from: 'node_modules/experimental-pathkit-asmjs/bin/pathkit.js.mem' }
+            { from: 'node_modules/pathkit-asmjs/bin/pathkit.js.mem' }
         ])
     );
 
 If webpack gives an error similar to:
 
-    ERROR in ./node_modules/experimental-pathkit-asmjs/bin/pathkit.js
+    ERROR in ./node_modules/pathkit-asmjs/bin/pathkit.js
     Module not found: Error: Can't resolve 'fs' in '...'
 
 Then, add the following configuration change to the node section of the config: