Move JS interface definition to a subdirectory

Author: magik6k

README.md

@@ -82,7 +82,7 @@ test.all(common)
 
 ## API
 
-In order to be considered "valid", an IPFS core implementation  must expose the API described in [/API](/API). You can also use this loose spec as documentation for consuming the core APIs. Here is an outline of the contents of that directory:
+In order to be considered "valid", an IPFS core implementation must expose the API described in [/SPEC](/SPEC). You can also use this loose spec as documentation for consuming the core APIs. Here is an outline of the contents of that directory:
 
 - **Files**
   - [files](/SPEC/FILES.md)
@@ -102,6 +102,11 @@ In order to be considered "valid", an IPFS core implementation  must expose the
   - [Miscellaneous](/SPEC/MISCELLANEOUS.md)
   - [config](/SPEC/CONFIG.md)
 
+Language-specific interface definitions and tests are in their directories:
+
+- [JavaScript](/js/src)
+- Go (WIP)
+
 ## Contribute
 
 Feel free to join in. All welcome. Open an [issue](https://github.com/ipfs/interface-ipfs-core/issues)!

src/block.js renamed to js/src/block.js

@@ -2,7 +2,7 @@
   "name": "interface-ipfs-core",
   "version": "0.41.1",
   "description": "A test suite and interface you can use to implement a IPFS core interface.",
-  "main": "src/index.js",
+  "main": "js/src/index.js",
   "scripts": {
     "test": "exit 0",
     "lint": "aegir lint",
@@ -13,8 +13,8 @@
     "coverage-publish": "exit 0"
   },
   "files": [
-    "src/",
-    "test/"
+    "js/src/",
+    "js/test/"
   ],
   "repository": {
     "type": "git",