BladeRunnerJS Sprint Demos

by Andy Berry on 08 Nov 2013

Read our latest: The year so far & 1.0 update.

What have these guys been doing for the past 2 weeks?

As you may, or may not know, BladeRunnerJS (BRJS) is a project born from an internal project at Caplin and has their continued sponsorship. Infact all of the core BRJS developers are Caplin developers. At Caplin we practice SCRUM and in doing so we divide tasks up in to 2 week sprints and at the end of every sprint we demo what was achieved to our stakeholders.

Since BRJS is now an open source project we have gained a lot more potential stakeholders; everyone in the JavaScript community. We wanted to address this and provide continual updates and value to all of our stakeholders.

So consider these posts your sprint demos.

So what have we actually done?

Following our initial release last sprint, we have started work on our new Bundler Plugin architecture allowing Bundlers to be written by anyone; more file types & bundles to be supported; and more complex use-cases such as source maps to be supported. This has been the key focus this sprint and will be continued next sprint where we hope to finish this stream of work.

There have been a number of smaller bug fixes, including feedback related to browser issues when running JavaScript tests, and a focus on our CI builds and infrastructure. Emitr, Fell and Topiary - our general purpose JavaScript libraries that are used within BRJS - are now running (and passing) in Travis CI using Sauce Labs for their browser tests. There has also been work to automate our GitHub release workflow; making use of GitHub’s API to calculate closed issues, create the release and upload the released binary. A blog post on this is soon to follow since this is a topic we hope others will find useful.

Want to have a look at the release in more detail? Have a look at our GitHub release and why not have a play around with BRJS and let us know what you think?

comments powered by Disqus