tridactyl/src/content.ts

/** Content script entry point */

// Be careful: typescript elides imports that appear not to be used if they're
// assigned to a name.  If you want an import just for its side effects, make
// sure you import it like this:
import "./keydown_content"
import "./commandline_content"
import "./excmds_content"
import "./hinting"

console.log("Tridactyl content script loaded, boss!")
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			`/** Content script entry point */`

			`// Be careful: typescript elides imports that appear not to be used if they're`
			`// assigned to a name. If you want an import just for its side effects, make`
			`// sure you import it like this:`
			`import "./keydown_content"`
			`import "./commandline_content"`
			`import "./excmds_content"`
hinting: First working version state.ts also reworked into a sexy new machine. Check it out! 2017-11-09 00:41:07 +00:00			`import "./hinting"`
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
			`console.log("Tridactyl content script loaded, boss!")`