tridactyl/tsconfig.json

{
  "compilerOptions": {
    "moduleResolution": "Node",
    "noImplicitAny": false,
    "noEmitOnError": true,
    "outDir": "build/tsc-out",
    "sourceMap": true,
    "target": "ES2017",
    "lib": ["ES2017","dom", "dom.iterable"],
    "typeRoots": ["node_modules/@types", "node_modules/web-ext-types/"],
    "alwaysStrict": true,
    "experimentalDecorators": true,
  },
  "include": [
    "./src/**/*"
  ],
  "exclude": [
    "./src/**/*.test.ts"
  ]
}
Initial typescript experiments. 2017-03-02 17:45:38 +00:00			`{`
			`"compilerOptions": {`
completions: add fuse.js and html-tagged-template 2017-11-16 18:12:18 +00:00			`"moduleResolution": "Node",`
Initial typescript experiments. 2017-03-02 17:45:38 +00:00			`"noImplicitAny": false,`
			`"noEmitOnError": true,`
Convert to es6 modules Motivation: - Most test frameworks expect modules - I'm told they're the future Changes: - Every typescript source file is now an es6 module - Build system is now webpack (tho rollup makes nicer outputs) - Outputs of buildsystem are one js file per entry point (background, content, commandline_frame) - These bundled js files are generated by traversing the dependency graph of each entry point 2017-10-02 00:59:51 +01:00			`"outDir": "build/tsc-out",`
			`"sourceMap": true,`
Initial typescript experiments. 2017-03-02 17:45:38 +00:00			`"target": "ES2017",`
improve pagination: - prefer the canonical forms over fallback patterns (fixes rockpapershotgun.com, Discourse etc.): 1) link[rel] 2) a[rel] 3) a::text(pattern) - tighten fallback patterns (fixes Google, GitHub etc.) - remove site-specific patterns 2017-11-22 22:21:46 +00:00			`"lib": ["ES2017","dom", "dom.iterable"],`
build: use strict 2017-11-22 03:41:32 +00:00			`"typeRoots": ["node_modules/@types", "node_modules/web-ext-types/"],`
Build a performance counters system so I can start optimizing things Complete a circular buffer so we don't log too much data, config settings for turning it on and off (default off, becuase performance) and for changing the size of the buffer, an excmd for dumping the raw json so you can pore over it, and for when you just want to sanity-check yourself instead of groveling over your data for six days with a deep learning toolkit and three hundred CPUs of compute, an excmd for pretty-printing your stats in a nice histogram. I didn't think far enough ahead and only implemented the easy way to instrument a function, which is with a decorator. I'm getting _really_ angry at typescript not being able to handle decorators on free functions. bah. I'll figure out a good way to wrap free functions. Maybe just go the stupid route and make you change `export async function foo(args)` to `export foo = measured(async function(args) ...`. But that would break excmd parsing, so... :/ I think that I already want to do a refactor to break excmd.ts into a bunch of one-line wrappers referencing implementations spread throughout a bunch of libraries. This would go nicely with that. Other things I did while I was here: * Fix the ugliness we had with (window as any).tri by monkey-patching the tri property into the window object in tridactyl.d.ts 2018-09-03 03:13:42 -07:00			`"alwaysStrict": true,`
			`"experimentalDecorators": true,`
Convert to es6 modules Motivation: - Most test frameworks expect modules - I'm told they're the future Changes: - Every typescript source file is now an es6 module - Build system is now webpack (tho rollup makes nicer outputs) - Outputs of buildsystem are one js file per entry point (background, content, commandline_frame) - These bundled js files are generated by traversing the dependency graph of each entry point 2017-10-02 00:59:51 +01:00			`},`
			`"include": [`
			`"./src/*/"`
tests: add jest 2017-10-05 01:53:02 +01:00			`],`
			`"exclude": [`
			`"./src/*/.test.ts"`
Convert to es6 modules Motivation: - Most test frameworks expect modules - I'm told they're the future Changes: - Every typescript source file is now an es6 module - Build system is now webpack (tho rollup makes nicer outputs) - Outputs of buildsystem are one js file per entry point (background, content, commandline_frame) - These bundled js files are generated by traversing the dependency graph of each entry point 2017-10-02 00:59:51 +01:00			`]`
Initial typescript experiments. 2017-03-02 17:45:38 +00:00			`}`