All the examples are in yaml, that can be useful to add some examples on the JSON format

https://atomiks.github.io/30-seconds-of-css/#truncate-text

https://github.com/kantord/bottoml.in-e imports the just-dashboard module to show one way it can be used with ready-written gists and data files.
I wanted to have a collection of related files in one single gist so thought to look at the code to see how locked into the appended gist URL format you were. It seemed that you detected input file format initially by file extension so I guess the files need to end in .yml or .json etc?

Wasn't sure if the filename 'must' be called dashboard, as in dashboard.yml? I wanted to have pairs in the gist collection of files, t22-yml, t33.yml, t33A.json t33B.json etc

Wanted to group similar graphs in the same gist but that means a location.hash added to the url so a new regexp needed? For instance, I made this gist

https://gist.github.com/zawsx/84c95865d0613ce210a148421815e966

If contains two of your example files,
https://gist.github.com/zawsx/84c95865d0613ce210a148421815e966#file-g22nutri-json
and
https://gist.github.com/zawsx/84c95865d0613ce210a148421815e966#file-t22-yml

Explicit support for hashes might also bring the possibility of adding #myswitch (e.g. #local, #remote, #debug) so as to maybe bring more flexibility to the segment count approach? My localhost test of the bottomline server wouldn't resolve to the pattern I was expecting - localhost:8080/reponame by default, I got confused as localhost:8080/example worked but not localhost:8080/reponame/example

It seemed that the 'e' in
http://bottoml.in/e/ is hardwired so I thought to split it out (making it 'g' for gist' etc). If you were to kindly add this facility, it would mean I could keep pace better with any future enhancements.

Install Airbrake in 2 easy steps:

Step 1: Add the library
Include via CDN:

<script src="https://cdnjs.cloudflare.com/ajax/libs/airbrake-js/1.0.4/client.min.js"></script>

We also support installation via npm and Bower.

Step 2: Copy this config snippet to your app.js file

(You can find your project ID and API KEY with your project's settings):

var airbrake = new airbrakeJs.Client({
  projectId: <Your project ID>,
  projectKey: '<Your project API Key>'
});
airbrake.addFilter(function (notice) {
  notice.context.environment = 'production';
  return notice;
});

To test that Airbrake has been installed correctly in your JavaScript project, just open up the JavaScript console in your internet browser and paste in:

airbrake.notify('hey there!')

Visit official GitHub repo for more info on alternative configurations and advanced options.

When using just-dashboard, you've kindly provided the option to submit ready-written dashboard and data files. With this, however, the bundle.js (as used for one of your simple pie chart examples for instance) is 907kb ([http://bottoml.in/e/kantord/2973bdd4ad689642562018bb4091ffbd]). Doesn't that make the idea a bit restricted in the width of uses? I had hoped to use it in a sort of 'i-frame' manner (without the iframe of course) as I think you intend.
However, in a text and graphics-heavy page, adding 1Kb to that page weight for a graph makes it noticeably slow to load when I try it - will people for the graphs to load whilst browsing the page, especially on mobile? Obviously caching will alleviate massively but for me, it'll only be one page per website so that doesn't help.
A news article might well have a page weight of 1Mb. If it were to include an auto-generated graphic (or set of graphics), generated by just-dashboard (as in http://bottoml.in/e/kantord/2973bdd4ad689642562018bb4091ffbd), there would be a further delay, after the 'main' page has loaded.
Maybe if the just-dashboard bundle.js could somehow be able to use async defer from the calling (1Mb) page, then the delay wouldn't be noticeable? Destroy some simplicity of use, so maybe as an option?

Add magic default values to dropdown

• ~first should select the first option
• ~last should select the last option

The render method should use 'file_loader' to load files with.
file_loader(filename) should return file contents.

This would be useful:

• On bottoml.in/e/ to enable loading other files from the Gist
• In just-dashboard-desktop to load other files from the file system

Had to remove the single quotes around './src/index.js' in package.json for it to work under windows - here's them removed:
"manual-test": "webpack-dev-server ./src/index.js --hot --inline --output-filename 'bundle.js'"

env variable assignments in package.json scripts don't work out of the box in W10 on mine. WEBPACK_ENV for instance.

The Makefile won't work under windows as make isn't native so the examples docs can't be compiled.

https://github.com/kantord/bottoml.in-e imports the just-dashboard module to show one way it can be used and outputs bundle.js
When I complile it, I'm actually getting bundle.js split into two parts as my webpack output, 625kb and 2548Kb. Looking back at the dashboard include, my dashboard.js is 3781kb and my vendors bundle 3335Kb
Is there a minimisation option I can take as I can't figure out why my bundle is 2171kb, more than double yours?

Hi!
I'm triying to create a page with multiple chars in same page, but I don't understand this lib, is server or client side?
How can I use with a single file in client, or make functional in server, whatever works is valid to me.
Thanks :)

Create a component gallery that

• Has an automatically generated screenshot for each component
• Example code to generate such screenshot
• Organized by category (text / input / chart / etc.)

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Hi! Thanks for doing this, it looks excellent!
Sorry if this is not really an issue - I couldn't figure the code out and hope it might help other idiots like me :)

I downloaded and installed it, then
npm i -s
Is there another step I need to take? I see the travis setup which I presume is for CI

Ran
npm run dev
Had to modify node_modules\webpack-cli\bin\webpack.js to
statsPresetToOptions = require("../../webpack/lib/Stats.js").presetToOptions;

Got to this point:

Can't figure out what to do next. Looked at the docs but they seem to be GHpages for https://kantord.github.io/just-dashboard/ ?

Basic problem is that I don't understand how the back end is arranged or what the front end code that calls the back end looks like? Looks as if jq-web is used to parse the yaml file? Couldn't figure out the route from api endpoint to the parser. Wanted to try everything locally.

manual_test.html for example, contains this:

Can't figure out what to put in manual_test.js

Maybe be really helpful if there was a version of manual_test.js (say, demo.js) in dist so that,say, demo,html would run locally?

Once again, sorry for being an idiot.

Instead of having attr:loader attr:query etc., data should be modified like this:

• Data should be an array
• If data x is not an array, it's interpreted as [x]

Each element in the array can be

• A "magic" string that is parsed into an array of loader objects
• An object with one key and one value (e. q. {graphQl: ["asdf"]} etc.)

The first loader receives undefined as input argument. All the other loaders receive the result of the first loader as argument.

Hello very cool library,

But that can be cool to provide this dashboard as a standalone library... So we can make pages without install webpack, etc... just load the lib and the conf

See:
https://bottoml.in/e/kantord/05825569b6c59aa7a402af0ec2689095