bismuth/tsconfig.json

{
  "compileOnSave": true,
  "compilerOptions": {
    "target": "es2016",
    "noEmitOnError": false,
    "removeComments": true,
    "lib": ["es5", "ES2015", "ES2016"],
    "alwaysStrict": true,
    "strict": true,
    "moduleResolution": "node",
    "module": "ES6",
    "plugins": [
      {
        "transform": "ts-auto-mock/transformer",
        "cacheBetweenTests": false
      }
    ]
  },
  "typedocOptions": {
    "entryPoints": ["src"]
  },
  "include": ["src/**/*"]
}
convert to typescript 2018-11-07 18:07:04 +03:00			`{`
Use npm scripts and wrap makefile around it Advantages: - Building description is more readable (top to bottom) - Build step is extracted from package step - Abstraction layers are not mixed within the tools ("Scripts describe how to build, Npm calls scripts, Make calls Npm" instead of "Make describes build, calls Npm") - No duplication of package description in Makefile and package.json 2021-08-26 22:32:59 +03:00			`"compileOnSave": true,`
			`"compilerOptions": {`
feat!: use esbuild for compiling script 2021-09-10 22:37:04 +03:00			`"target": "es2016",`
Use npm scripts and wrap makefile around it Advantages: - Building description is more readable (top to bottom) - Build step is extracted from package step - Abstraction layers are not mixed within the tools ("Scripts describe how to build, Npm calls scripts, Make calls Npm" instead of "Make describes build, calls Npm") - No duplication of package description in Makefile and package.json 2021-08-26 22:32:59 +03:00			`"noEmitOnError": false,`
			`"removeComments": true,`
build: :memo: use SPDX statements for licencing 2021-09-04 16:33:51 +03:00			`"lib": ["es5", "ES2015", "ES2016"],`
Use npm scripts and wrap makefile around it Advantages: - Building description is more readable (top to bottom) - Build step is extracted from package step - Abstraction layers are not mixed within the tools ("Scripts describe how to build, Npm calls scripts, Make calls Npm" instead of "Make describes build, calls Npm") - No duplication of package description in Makefile and package.json 2021-08-26 22:32:59 +03:00			`"alwaysStrict": true,`
feat!: compile as module This breaks the script for now, but it works 2021-08-30 14:04:48 +03:00			`"strict": true,`
build: use node resolution to fix building 2021-09-05 01:03:51 +03:00			`"moduleResolution": "node",`
test: :white_check_mark: add a few basic tests with mocks Tests directory probably will be used for integration tests. 2021-09-15 20:18:23 +03:00			`"module": "ES6",`
			`"plugins": [`
			`{`
			`"transform": "ts-auto-mock/transformer",`
			`"cacheBetweenTests": false`
			`}`
			`]`
Use npm scripts and wrap makefile around it Advantages: - Building description is more readable (top to bottom) - Build step is extracted from package step - Abstraction layers are not mixed within the tools ("Scripts describe how to build, Npm calls scripts, Make calls Npm" instead of "Make describes build, calls Npm") - No duplication of package description in Makefile and package.json 2021-08-26 22:32:59 +03:00			`},`
docs: basic documentation generation 2021-08-27 19:57:11 +03:00			`"typedocOptions": {`
build: :memo: use SPDX statements for licencing 2021-09-04 16:33:51 +03:00			`"entryPoints": ["src"]`
docs: basic documentation generation 2021-08-27 19:57:11 +03:00			`},`
build: use node resolution to fix building 2021-09-05 01:03:51 +03:00			`"include": ["src/*/"]`
build: :memo: use SPDX statements for licencing 2021-09-04 16:33:51 +03:00			`}`