This repository was archived by the owner on Oct 9, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 9, 2020. It is now read-only.
Async/await is not working with this pattern #68
Description
This one works:
//boot.js
var main = require('./main.js')
main.boot()
//main.js
export async function boot() {
await new Promise(function(resolve, reject) {
console.log('hello world');
setTimeout(function() {
resolve();
}, 1000);
})
console.log('hello world after 1s!');
}
This one works with webpack but systemjs:
//boot.js
var main = require('./main.js')
//main.js
(async function boot() {
await new Promise(function(resolve, reject) {
console.log('hello world');
setTimeout(function() {
resolve();
}, 1000);
})
console.log('hello world after 1s!');
})()
Not sure is it an issue
Edit:
Works after adding this:
export var p = 5;
More precisely, in configuration:
meta: {
'./js/main.js': {
format: 'esm'
}
}
Activity
OrKoN commentedon Oct 21, 2016
@rf00 AFAIK, systemjs classifies a module as an ES6 module only if there are import/export statements. Otherwise it assumes it is ES5 and does not apply the transpiler.
rf00 commentedon Oct 21, 2016
@OrKoN It works!
aluanhaddad commentedon Aug 15, 2017
Sort of. Basically, if there is no out-of-band1 metadata specifying the format of a package, files are parsed and a format is inferred based on a number of factors including the presence of
import/exportstatements.It is often desirable to specify the source module format declaratively as this may improve performance and does not depend on heuristics2
1 Out of band in this context would be package configuration such as
It may also come in the form of overrides in the jspm registry
{ "format": "amd" }or overrides explicitly provided when installing with jspm on a case by case basis
$ jspm install jquery --override "{format : 'cjs'}"2 See the SystemJS documentation for module-format-detection.