-
Notifications
You must be signed in to change notification settings - Fork 33
plugin-babel does not work as described in documentation #56
Comments
If just using systemjs, you probably want to make a build of the Babel
|
@guybedford you mean if i have additional plugins like ( transform-decorators-legacy, etc ) i have to build them before? like this: builder.config({
map: {
'systemjs-babel-build': 'path/to/systemjs-plugin-babel/systemjs-babel-node.js',
'babel-plugin-transform-class-properties': './node_modules/babel-plugin-transform-class-properties/lib/index.js',
'babel-plugin-transform-decorators-legacy': './node_modules/babel-plugin-transform-decorators-legacy/lib/index.js',
'babel-plugin-transform-function-bind': './node_modules/babel-plugin-transform-function-bind/lib/index.js',
}
});
builder.bundle('app/bootstrap', 'out-bundle.js'); Is this behavior on the fly possible without bundling? |
@SerkanSipahi the alternative in Node is to use builder.config({
'babel-plugin-transform-class-properties': '@node/babel-plugin-transform-class-properties'
}); but then it won't work in the browser. The browser use case is exactly what jspm is designed to assist with. |
@guybedford, sorry for the late reply ! I use my proven use case -> compile everything with babel and using as module loader systemjs ( with transpiler: false ). This works fine for me. |
@guybedford : After a long time i have a project where im using "only" systemjs with plugin-babel. The problem is that Systemjs cant initialize the plugin files. I get always an error 404. Its try to load from wrong location:
wrong !
correct would be (starting with node_modules):
What im doing wrong?
Info
The text was updated successfully, but these errors were encountered: