3 Commits

Author	SHA1	Message	Date
Jonathan Lipps	422142302f	chore: publish ... - appium@2.0.0-beta.49 - @appium/base-driver@9.2.0 - @appium/base-plugin@2.1.0 - @appium/doctor@2.0.2 - @appium/docutils@0.1.2 - @appium/driver-test-support@0.3.2 - @appium/execute-driver-plugin@3.0.2 - @appium/fake-driver@5.1.0 - @appium/fake-plugin@3.1.0 - @appium/images-plugin@2.0.2 - @appium/opencv@2.0.2 - @appium/plugin-test-support@0.3.2 - @appium/relaxed-caps-plugin@1.0.1 - @appium/schema@0.2.0 - @appium/support@3.1.0 - @appium/test-support@3.0.2 - @appium/tsconfig@0.2.0 - @appium/typedoc-plugin-appium@0.3.0 - @appium/types@0.8.0 - @appium/universal-xml-plugin@1.0.1	2023-01-13 13:09:28 -08:00
Christopher Hiller	7942118429	chore(tsconfig): strip internal stuff from declarations ... typedoc respects this flag as well	2023-01-10 09:32:46 -08:00
Christopher Hiller	7d7b510a03	feat: create @appium/tsconfig ... For the TypeDoc plugin to correctly pull information from `@appium/types` and `@appium/base-driver`, they both need `tsconfig.json` files. They currently _have_ `tsconfig.json` files, but they extend base configs in the monorepo root, which is problematic. Moving the configs into a package seems reasonable. Further, all packages must publish `tsconfig.json`. There's precedent for publishing a `tsconfig.json` this way. FWIW the `paths` and `references` fields in the `tsconfig.json` files seem to be ignored by TypeDoc, so we can get away with this.	2023-01-03 12:50:53 -08:00