-
Notifications
You must be signed in to change notification settings - Fork 282
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
Feature/465 bundler #504
Feature/465 bundler #504
Conversation
using it for CLI building of resources
Allow changing the include logic for html/css/code
client bundler with the current asset combination
ss.bundler provides common functionality
No need to support Node JS without Array.indexOf
bundler.define returns the destination paths so pack can manage the output files.
webpack bundler for trying out
sourcePaths common logic notes paths relative to /client rather than type specific.
Templates are in '/client/templates' by default, but can be outside using paths starting with './'
Require path starting with ./ is relative to /client, this must also be passed in the dev time URL.
Run through them the same way when packing and adding html tags.
logical path/dir for system modules and libraries optional wrap system modules
Very nice. |
Plus load/unload tweaks
Used in tests and to clean up before unloading/reloading process
#465 bundler basics. More tests required.
Can someone please ‘splain the @coveralls account? |
It's an app that monitors the PR for drops in test coverage, isn't it. I've never used it so I just assume things. Perhaps Paul can give more details |
It's a Code Coverage service which monitors code coverage % on your repos. If you integrate it with your Github repo then it will check commits and post the results to the comments section in the PR. |
Word. Thx! |
Bundler API allows you to use a specific custom bundler for a view in your SS application.