ssa.js | Construction of minimal SSA form | Form library

You have a circular dependency. The solution is to have a third class that will require both and use whatever code you have from ClassA in ClassB and the other way around.

My currently working solution is to use an additional "package"-script file, which then encapsulates all classes.

Yes, this is the best practice. The "package" script file is typically called index.js placed in the directory of the package, as that's what the folder path is resolved to when importing.

importing this script in every new class

No, you should not do that. It introduces a circular dependency. As long as your module doesn't depend on any of the other classes, it should not import anything. There is no "package declaration", the module is a standalone file with its own dependencies.

Notice also that you shouldn't export your class twice from the module, the default export is enough. So you'd use

Typings are not supposed to be used for linting the libraries themselves, you can't make the IDE (or tsc compiler) to use them for this purpose. I'd suggest using JSDoc annotations instead, like:

you need to add static keyword to use as a class method,

you're missing a . in your extensions webpack config extensions: [".js", ".jsx", ".tsx", "ts"]. ts should be .ts

In a comment you've clarified what you're trying to do (it's also a code comment in the question):

How can I call aFunction() from classA then?

You'd do that by giving the code in ClassA access to your instance. You might pass it to the constructor which could save it as an instance property, or you might pass it to doSomething.

Here's an example passing it to the constructor:

No, it is not possible to remove an ES6 (ECMA2015) class declaration from memory.

In regards the script element, the JavaScript engine parses and runs the script after it has been loaded. Running the script declares ClassA in global scope. Deleting the script element doesn't remove the declaration - in the same way deleting the source file of a compiled program won't delete an object or executable file already created from it.

ES6 also introduced special arrangements for let variables, constants and classes: they are block scoped and may not be re-declared in the same block or in global scope. Trying to do so is considered a programming error:

A stub is actually required for this:

You could try something like :