Remove separate TypeScript compilation.

Current situation Currently, most of the .ts files that we have are compiled through Webpack, only a few remaining files and folders are compiled separately with TypeScript. The files and folders are listed in tsconfig.json. These last remaining files and folders are also the reason why we need to have two separate ts configs (tsconfig-for-compile-check.json).

Expected solution Remove remainig files and folders from tsconfig.ts:

• karma-globals.ts
  • can be removed after last GLOBAL is removed from frontend tests

After all the files and folders are removed, all the separate TypeScript compilations should be removed and also all references to local_compiled_js folder that was generated by that compilation should be removed.

The last step should be to replace tsconfig.json with tsconfig-for-compile-check.json.

[kevinlee12]

It’s fine to do the second one, since the first option isn’t great. However, if @Jamesjay4199 has other suggestions, I’m all ears for that one.

[vojtechjelinek]

@Jamesjay4199 Do you have any suggestion regarding the last global in FE tests?

typings folder should be obvious from the issue description. extensions/ckeditor_plugins contains the pre plugin which is loaded in ck-editor-4-rte.directive.ts but since it is loaded directly by CKEditor it needs to be some standalone JS file. Two solutions are proposed both are creating a bit of exception in our codebase:

• The first is to add this file as an entry point into webpack.common.config.ts, that would mean it would be compiled from TypeScript to JavaScript by webpack and provided into the webpack_bundles folder, but I now realize that this would also mean that we would need to handle prod mode when the filename would also contain hash which could be quite complicated.
• The second is to change the file into JavaScript (this might mean just to change the .ts to .js but also maybe some change in the file content) and have it as an exception. @kevinlee12 would this be okay from your POW?