chore: Fix type definitions

[park9140]

Fixes exported type definitions so that you can import from typescript using import { Zone } from 'zone.js' and not have the compiler complain about it not being a module.

Resolves #297, still needs a resolution to access the correct ZoneSpec via import without declaring a module manually.

[PatrickJS]

you could also add this snippet to the zone.ts file

// Ensure this is treated as a module.
declare module "zone.js" {}

[park9140]

@gdi2290 I considered that. I just figured it was better to push the project toward a correct implementation, rather than the current clumsy mish mosh of ambient dependency, and external modules.

[PatrickJS]

no worries, your version is correct and preferred 👍

[mhevery]

We can not add this code here. If we do then Zones will be included in the async-test.js bundle as well as zone.js bundle.

Zone's is meant as a polyfil, and so it should be ambiently available.

[mhevery]

Thanks for you hard work, but we can't accept this PR. The issue is that Zone needs to be treated as if it is part of platform. ie. it needs to have ambient definition. Your change makes it so that it must be imported explicitly.