* Remove deprecated baseUrl option
https://devblogs.microsoft.com/typescript/progress-on-typescript-7-december-2025/
* Fix incorrect imports from build package
It's safe to change the paths.build in tsconfig.json – the build package
has no src directory, so there's definitely no imports which utilize
this path.
* Fix remaining incorrect imports
* Remove wildcard path
* Make `web/design` a separate TypeScript project
* Fix compile errors
It seems that making `web/design` a separate project slightly changes the behavior of type inference
* Add types for `css` prop instead of importing it implicitly from `@emotion/core`
* Move `styled-system.d.ts` to `packages/design`
The `styled-system` package is installed there (it has to be reachable from the declaration file).
* Remove `border` from `FeatureHeader`
We don't pass any props that would use it. That's also the only import of `styled-system` outside of `packages/design`.
* Remove `grpc` path, it is used only in one place
* Add functions to clone every gRPC method, so they can be passed over the context bridge
* Replace `@grpc/grpc-js` interceptors with `@protobuf-ts/runtime-rpc` ones
* Replace string check with check on metadata, add missing `AddMetadataToRetryableError`
* Add `pin` to sensitive properties
It's needed because now we also log a passwordless login stream call.
* Add `cloneClient` method to clone the entire gRPC client
* Switch tests to `TshdRetryableError`
* Improve comments
* Move `cloneClient` and `cloneAbortSignal` to the top of the file
* Simplify condition
* Lowercase logs
* Check if the error is `RpcError` using `instanceof`
* Log error object instead of `[object Object]`
* Do not export call specific types
* Wrap gRPC calls in `createClient` to allow passing the errors over the context bridge (#39230)
* Regenerate protos with the `protobuf-ts` client
* Enable `strictBindCallApply` so `.bind()` results have correct types (instead of `any`)
This is needed for wrapping calls in `createClient`.
* Use `protobuf-ts` client instead of `grpc-js` one
* Convert `createClient` to use `protobuf-ts` response style, clone each call
* Switch callsites to `cloneAbortSignal`
* Replace `error.message` checks with a proper check on the error status code
* Clone the entire client instead of each method separately
* Correct the error `cause` in `ResourceSearchError`
* Remove `params.sortBy` defaults, always set `startKey` to string
* Use a simpler type for `reportUsageEvent`
* Fix interceptor test
* Ignore TS error in `highbar.ts`
* Update eslint-plugin-jest to 27.9.0
https://github.com/jest-community/eslint-plugin-jest/blob/main/CHANGELOG.md#2600-2022-01-24https://github.com/jest-community/eslint-plugin-jest/blob/main/CHANGELOG.md#2700-2022-08-28
I switched plugin:jest/all to plugin:jest/recommended, since /all just
activates every rule in the package. This might have been fine when this
package was added a couple of years ago, but it doesn't make sense anymore.
27.0.0 requires parserOptions.project to be set, but this returned an error:
0:0 error Parsing error: ESLint was configured to run on
`<tsconfigRootDir>/web/packages/teleport/vite.config.mts` using `parserOptions.project`:
/users/rav/src/teleport/tsconfig.json
However, that TSConfig does not include this file. Either:
- Change ESLint's list of included files to not include this file
- Change that TSConfig to include this file
- Create a new TSConfig that includes this file and include it in your parserOptions.project
I updated tsconfig.node.json so that it applies only to .mts files, as
I understand that was the original intention.
* Autofix jest/valid-title
* Do not set parserOptions.project
It makes ESLint slower by ~20s and it is not needed for recommended rules
from eslint-plugin-jest.
We use Vite to compile TS files, so tsc is used merely for type-checking.
Setting noEmit to true makes sure that other tools which use tsc (like
editor plugins) do not make tsc compile code.
outDir is removed as it's not needed if we do not use tsc to compile code.
* Specify the path for protoc-gen-ts so it doesn't use @protobuf-ts/plugin
* Add TypeScript protobuf generation
* Add the TypeScript generated protobufs to gitattributes
* Add the generated TypeScript protobuf files
* Add `gen/proto/ts` everywhere `gen/proto/js` is referenced
* Use npm exec to avoid a hard-coded path
* Add --yes flag to npm exec
* Also update JS generation to use npm exec
* Specify version number in buf config
* Re-run make grpc
* Format tsconfig.json
* Add toEventuallyBeTrue custom matcher
The whole of web/packages/build was ignored in tsconfig.json, but it
turns out we only need to ignore the vite dir to make the type check
pass.
* Add implementation of agent cleanup daemon
* Refactor existing AgentRunner
* Refactor logging in cleanup daemon
* Provide a path to cleanup daemon in dev & prod
* Spawn cleanup daemon after spawning agent
* Add logging to agent cleanup daemon
* Document custom exit codes
* Replace inheritStdio with top level stdio variable
* Remove unnecessary backticks
* Add logsDir to RuntimeSettings
* Refactor how cleanup daemon is included in dev & packaged app
If tsconfig doesn't have an `outDir` option set, VS Code shows multitude of errors of the following kind:
```
Cannot write file '/Users/bartosz/code/teleport/e/web/teleport/babel.config.js' because it would overwrite input file.
```
* Adjust go_package of lib/prehog Go protobufs
This makes them follow the pattern set out by api/proto and proto.
* Adjust go_package of lib/teleterm Go protobufs
* Use single buf.gen.yaml to generate JS protos
This also entailed changing the location of lib/teleterm protos and changing
the value of their package specifier to match the conventions in other parts
of the codebase. This is a breaking change but that is fine for Connect
as the protos are used locally only and each build ships with matching
protobufs.
* Make web/packages/teleterm use protobufs from gen-proto-js
We used to copy protobufs over to web/packages/teleterm/src/services/tshd
since webapps used to be in a separate repo.
This is no longer the case, so we can just make teleterm use protobufs
from gen-proto-js.
* Move prehog & teleterm protos into proto/teleport/lib
* Generate JS protos to gen/proto/js
* Move lib/teleterm Go protobufs to gen/proto/go
* Move lib/prehog Go protobufs to gen/proto/go
* Rename lib/teleterm proto package
* Re-enable linter rules for teleterm & prehog
* Update prehogv1 path in usagereporter_test.go
* Use except instead of ignore_only to allow Google API-style responses
* Add UNARY_RPC to api/proto & proto
* Ignore gen/ when running addlicense
* buf-js.gen.yaml: Remove comment about lack of go_package for JS
* Move prehog protos to proto/prehog/v1alpha
* Adjust prehog's go_package to match proto package
* Move tsconfig.json to root dir
At the moment, it looks like the TS language server has problems with
recognizing imports when editing files inside e/web.
I figured this is probably because tsconfig.json is in web, so the lang
server doesn't recognize it when editing files from e/web.
* Remove web/Dockerfile and web/Makefile
* Misc updates to readme
* Fix links in readme
Ryan Clark