Poul Kjeldager Sørensen

I tried this but got an issue. ``` Severity Code Description Project File Line Suppression State Error TS2322 (TS) Type 'Promise' is not assignable to type 'Promise'. Type 'typeof import("C:/dev/IO-Board.Management.Portal/apps/IO-Board.Management.Portal/src/components/OLMap")'...

The component look like: ``` @Component export default class OLMap extends tsx.Component{ ... } ```

With the latest versions of stable, or dev, i do not get the experience you have above. I will try to create a minimal repro with the issue.

Just to show it.   

Here is a repro: https://github.com/pksorensen/tsx-issue just run npm install and npm run dev and you should see the build errors @wonderful-panda

I will try to downgrade- only reason I tried to use 3.0 was that I could not get it working. I will report back Sent from mobil ________________________________ From: wonderful-panda...

I tested this, but it parses the links for TOS wrong when using netstandard2.0  resulting in ``` ACMESharp.AcmeClient+AcmeWebException: Unexpected error +Response from server: + Code: BadRequest + Content: {...

I switched to certes also yesterday instead of making it work. Its nice and the dependency graph is also more clean.

Hi again, sorry for the delay. I think its related with changes to how npm resolves peerdependencies in latest versions of npm. I am working around it by npm install...

Byte serving could be an interesting case, where the hole tile contains all data and may be several mb large. Then maybe having a seperate index file or the first...