fix(types): update type deps

cli/pbts.js

@@ -144,7 +144,7 @@ exports.main = function(args, callback) {
             var output = [];
             if (argv.main)
                 output.push(
-                    "// DO NOT EDIT! This is a generated file. Edit the JSDoc in src/*.js instead and run 'npm run types'.",
+                    "// DO NOT EDIT! This is a generated file. Edit the JSDoc in src/*.js instead and run 'npm run build:types'.",
                     ""
                 );
             if (argv.global)

index.d.ts

@@ -1,4 +1,4 @@
-// DO NOT EDIT! This is a generated file. Edit the JSDoc in src/*.js instead and run 'npm run types'.
+// DO NOT EDIT! This is a generated file. Edit the JSDoc in src/*.js instead and run 'npm run build:types'.
 
 export as namespace protobuf;
 

tests/README.md

@@ -5,7 +5,7 @@ It is essential that tests only use the cross-platform API that is also availabl
 * Use `load`, not `loadSync`
 * Use `Reader.create`, not `BufferReader`
 * Use `Writer.create`, not `BufferWriter`
-* It is safe to use `Long`
+* It is safe to use `Long`, but TypeScript tests must import the type from `"long"`
 
 If it's absolutely inevitable for your test case to use node-specific features, you can still use this pattern:
 

tests/data/mapbox/vector_tile.d.ts

@@ -1,4 +1,6 @@
 import * as $protobuf from "../../..";
+import Long from "long";
+
 export namespace vector_tile {
 
     interface ITile {

tsconfig.json

@@ -2,6 +2,7 @@
     "compilerOptions": {
         "target": "ES5",
         "experimentalDecorators": true,
-        "emitDecoratorMetadata": true
+        "emitDecoratorMetadata": true,
+        "esModuleInterop": true,
     }
 }