🐞 bug report
Affected Package
The issue is caused by package @angular/packages/zone.js
Is this a regression?
Yes, worked in 0.9.1
Description
When loading modules using requireJS, the zone is lost.
🔬 Minimal Reproduction
The following in index.html, which should also include zone.js
<script src="zone.js"></script>
<script src="../node_modules/requirejs/require.js"></script>
<script>
function testOne () {
Zone.current.fork({name:'one-zone'})
.run(() => new Promise((resolve) => {
// load one.js
requirejs(['one'], (one) => {
one();
resolve(one);
});
}));
}
// bootstrap
Zone.current.fork({ name: 'main' }).run(testOne);
</script>
`
the entire contents of one.js, in the same folder of index.html
console.log('outside module "one" : ' + window.Zone.current.name);
define(() => {
console.log('module "one": ' + window.Zone.current.name);
return () => {
console.log('module "one" function: ' + window.Zone.current.name);
}
});
In 0.10.X, all three console.logs report the name of the zone as the <root>, and not my one-zone.
With 0.9.1, I see the following:
outside module "one" : <root>
module "one": one-zone
module "one" function: one-zone
🌍 Your Environment
Angular Version:
angular: 10.1.0-next.6
zone.js: 0.10.3
requirejs: 2.3.6
🐞 bug report
Affected Package
The issue is caused by package @angular/packages/zone.js
Is this a regression?
Yes, worked in 0.9.1
Description
When loading modules using requireJS, the zone is lost.
🔬 Minimal Reproduction
The following in index.html, which should also include zone.js
the entire contents of one.js, in the same folder of index.html
In 0.10.X, all three console.logs report the name of the zone as the
<root>, and not myone-zone.With 0.9.1, I see the following:
🌍 Your Environment
Angular Version: