Add TypeScript typings for core & webpack

[zcei]

Hej guys 👋

I started tackling #246, for now only @webpack-blocks/core & @webpack-blocks/webpack to have a foundation, so we can discuss naming etc.

Afterwards we just need to add the proper index.d.ts to the blocks.

If I'm not mistaken there shouldn't be other changes necessary, at least VSCode gave me type hints in the sample app already, but I'll list some here for research:

• add typings to package.json(should be obsolete, as we comply to index.d.ts convention)
• add index.d.ts to webpack-blocks which exports types from sub-modules (should be infered from sub-module typings)
• find out which @types/ needs to be installed manually

[andywer]

Thanks for starting work on this, @zcei! Will have a deeper look into it :)

[zcei]

Actually returns a WebpackBlock

[andywer]

I think we have to agree upon some terminology. The term block, for instance, has always been a bit fuzzy. Providing explicit types is probably the ideal time to define it properly.

[zcei]

Initially I was thinking that a block is a self-contained, configurable portion of a Webpack Configuration - so actually entryPoint is the block, not entryPoint(), which could be a BlockInstance or similar.

Then a block is everything that has the signature (...args: any[]): BlockInstance, where BlockInstance = (current) WebpackBlock

[andywer]

Fair enough. I would follow your argumentation here, @zcei. BlockInstance is not very catchy, but should do for now.

[andywer]

We need to discuss terminology here, since most terms haven't ever been clearly defined.
Current state of affairs is:

Initially I was thinking that a block is a self-contained, configurable portion of a Webpack Configuration - so actually entryPoint is the block, not entryPoint(), which could be a BlockInstance or similar.

Then a block is everything that has the signature (...args: any[]): BlockInstance, where BlockInstance = (current) WebpackBlock

If someone has a better naming suggestion for BlockInstance, feel free to share it here 😉

[andywer]

Another term that might be discussable is WebpackBlockUpdater.

Maybe it's rather a WebpackConfigUpdater: It's actually so generic that it's not webpack-blocks-specific. And this name might transport more information. Objections?

[andywer]

Update: Let's better discuss this in the issue (#246) than in the PR.