-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't seem to work? #18
Comments
I'm using |
I think the command has changed to generate-config. Run systemjs --help to verify. |
Thanks. It now complains: :: exiting :: couldn't find a valid systemjs-tools config |
Damn. I recently changed how systemjs initializes itself. Just heading in to a meeting now. Can fix after that. |
No problem. Take your time. 🌷 |
@unional Just had a look, I actually use the config for {
...
"systemjs-tools": {}
...
} This will indicate to config builder where the root is. You can also customize the cache file location via {
...
"systemjs-tools": {
"cache": ".myCustomeCacheFile.json"
}
...
} |
@unional did this solve your issue? |
I see. Have not try it yet. |
Yes, and then it uses the file it finds to act as a 'root'. But can probably offer a default. Although this isn't high priority for me right now |
Could you add some documentation on how the cache works? Every time I run generate-config, it takes a long time to complete, and don't see any cache files created. |
I don't have time to write docs right now, since I'm right in the middle of exams, but you can take a look here It gets the cache out of the systemjs cache. You should see a |
There might be a bug with the cache generation, as I see a systemjs.cache file created but with contents of https://github.com/alexisvincent/systemjs-config-builder/blob/master/lib/index.js#L425 |
I follow the example to do:
// in an empty folder. yarn global add systemjs-tools yarn add systemjs systemjs-nodelibs systemjs-plugin-babel react react-dom systemjs config
But the
systemjs config
just exit and nogenerated.config.js
is created.The text was updated successfully, but these errors were encountered: