brut 0.17.0 → 0.18.0

data/brutrb.com/.vitepress/config.mjs

@@ -1,164 +0,0 @@
-import { defineConfig } from 'vitepress'
-import rdocLinker from './plugins/rdocLinker'
-import jsdocLinker from './plugins/jsdocLinker'
-
-// https://vitepress.dev/reference/site-config
-export default defineConfig({
-  title: "Brut RB",
-  description: "Documentation for the Brut.RB web framework.",
-  ignoreDeadLinks: [
-    /^https?:\/\/localhost/,
-  ],
-  head: [
-    ["link", { rel: "icon", href: "/favicon.ico" }],
-    [
-      "meta", {
-        property: "og:title",
-        content: "BrutRB Documentation"
-      }
-    ],
-    [
-      "meta", {
-        property: "og:type",
-        content: "website"
-      }
-    ],
-    [
-      "meta", {
-        property: "og:image",
-        content: "https://brutrb.com/SocialImage.png"
-      }
-    ],
-    ["script", {
-      defer: "",
-      "data-domain": "brutrb.com",
-      src: "https://plausible.io/js/script.js"
-    }
-    ],
-  ],
-  themeConfig: {
-    // https://vitepress.dev/reference/default-theme-config
-    search: {
-      provider: 'local',
-    },
-    nav: [
-      { text: 'Home', link: '/' },
-      { text: 'Getting Started', link: '/getting-started' },
-      { text: 'Overview', link: '/overview' },
-      { text: 'Brut API', link: '/api/index.html', target: "_self" },
-      { text: 'BrutJS', link: '/brut-js/api/index.html', target: "_self" },
-      { text: 'BrutCSS', link: '/brut-css/index.html', target: "_self" },
-    ],
-    outline: [ 2, 3] ,
-    sidebar: [
-      {
-        text: "Overview",
-        collapsed: false,
-        items: [
-          { text: "Getting Started", link: "/getting-started" },
-          { text: "Concepts", link: "/overview" },
-          { text: "Features", link: "/features" },
-          { text: "Directory Structure", link: "/dir-structure" },
-          { text: "Dev Environment", link: "/dev-environment" },
-          { text: "Tutorial", link: "/tutorial" },
-          { text: "Documentation Conventions", link: "/doc-conventions" },
-        ]
-      },
-      {
-        text: "Front-End",
-        collapsed: false,
-        items: [
-          { text: "Routes", link: "/routes" },
-          { text: "Pages", link: "/pages" },
-          { text: "Layouts", link: "/layouts" },
-          { text: "Forms", link: "/forms" },
-          { text: "Form Constraints", link: "/form-constraints" },
-          { text: "Handlers and Actions", link: "/handlers" },
-          { text: "Components", link: "/components" },
-          { text: "Flash and Session", link: "/flash-and-session" },
-          { text: "Space/Time Continuum", link: "/space-time-continuum" },
-          { text: "JavaScript", link: "/javascript" },
-          { text: "CSS", link: "/css" },
-          { text: "Assets", link: "/assets" },
-          { text: "BrutJS", link: "/brut-js" },
-        ]
-      },
-      {
-        text: "Back-End",
-        collapsed: false,
-        items: [
-          { text: "Database Schema", link: "/database-schema" },
-          { text: "Database Access", link: "/database-access" },
-          { text: "Seed Data", link: "/seed-data" },
-          { text: "Jobs", link: "/jobs" },
-          { text: "Business Logic", link: "/business-logic" },
-        ]
-      },
-      {
-        text: "Framework",
-        collapsed: false,
-        items: [
-          { text: "Configuration", link: "/configuration" },
-          { text: "Keyword Injection", link: "/keyword-injection" },
-          { text: "I18n", link: "/i18n" },
-          { text: "CLI / Tasks", link: "/cli" },
-          { text: "Deployment", link: "/deployment" },
-        ]
-      },
-      {
-        text: "Testing",
-        collapsed: false,
-        items: [
-          { text: "Unit Tests", link: "/unit-tests" },
-          { text: "End-to-End Tests", link: "/end-to-end-tests" },
-          { text: "Testing Custom Elements", link: "/custom-element-tests" },
-        ]
-      },
-      {
-        text: "Advanced Topics",
-        collapsed: true,
-        items: [
-          { text: "Route Hooks", link: "/hooks" },
-          { text: "Middleware", link: "/middleware" },
-          { text: "Instrumentation", link: "/instrumentation" },
-          { text: "Security", link: "/security" },
-          { text: "LSP Support", link: "/lsp" },
-        ],
-      },
-      {
-        text: "Recipes",
-        collapsed: true,
-        items: [
-          { text: "Alternate Layouts", link: "/recipes/alternate-layouts" },
-          { text: "Authentication", link: "/recipes/authentication" },
-          { text: "Custom Flash Class", link: "/recipes/custom-flash" },
-          { text: "Indexed Form Elements", link: "/recipes/indexed-forms" },
-          { text: "Managing Secrets in the Dev Environment", link: "/recipes/dev-env-secrets" },
-          { text: "Migration Basics", link: "/recipes/migrations" },
-          { text: "Styling Form Errors", link: "/recipes/form-errors" },
-          { text: "Text Field Component", link: "/recipes/text-field-component" },
-        ],
-      },
-      {
-        text: "Meta",
-        collapsed: false,
-        items: [
-          { text: "Why?!", link: "/why" },
-          { text: "ADRs", link: "/adrs" },
-          { text: "Roadmap to 1.0", link: "/roadmap" },
-          { text: "AI Declaration", link: "/ai" },
-        ]
-      },
-    ],
-
-    socialLinks: [
-      { icon: 'github', link: 'https://github.com/thirdtank/brut' }
-    ]
-  },
-  markdown: {
-    config(md) {
-      md.use(rdocLinker)
-      md.use(jsdocLinker)
-    }
-  }
-})

data/brutrb.com/.vitepress/plugins/jsdocLinker.js

@@ -1,34 +0,0 @@
-export default function jsdocLinker(md) {
-
-  const orig = md.renderer.rules.code_inline || function(tokens, idx, options, env, self) {
-    return self.renderToken(tokens, idx, options);
-  };
-
-  function toPageName(tag) {
-    if (tag == "cv") {
-      return "ConstraintViolationMessage"
-    }
-    else if (tag == "cv-messages") {
-      return "ConstraintViolationMessages"
-    }
-    else {
-      return tag
-        .split('-')
-        .map(s => s.charAt(0).toUpperCase() + s.slice(1))
-        .join('');
-    }
-  }
-
-  md.renderer.rules.code_inline = function(tokens, idx, options, env, self) {
-    const content = tokens[idx].content;
-    // If it matches a custom element pattern
-    const match = content.match(/^<brut-([a-z][a-z0-9\-]*)>$/);
-    if (match) {
-      const tag = match[1];
-      const pageName = toPageName(tag);
-      return `<a href="/brut-js/api/${pageName}.html" target="_self" rel="noopener" data-no-router><code style="white-space: nowrap">&lt;brut-${tag}&gt;</code></a>`;
-    }
-    // ...your existing Ruby class matcher, if you want both!
-    return orig(tokens, idx, options, env, self);
-  };
-};

data/brutrb.com/.vitepress/plugins/rdocLinker.js

@@ -1,18 +0,0 @@
-export default function rdocLinker(md) {
-
-  const orig = md.renderer.rules.code_inline || function(tokens, idx, options, env, self) {
-    return self.renderToken(tokens, idx, options);
-  };
-
-  md.renderer.rules.code_inline = function(tokens, idx, options, env, self) {
-    const content = tokens[idx].content;
-    // Only match Ruby class-like tokens
-    if (/^Brut::[A-Z][A-Za-z0-9_:]+$/.test(content)) {
-      const path = content.replace(/::/g, '/')
-      return `<a href="/api/${path}.html" target="_self" rel="noopener" data-no-router><code>${md.utils.escapeHtml(content)}</code></a>`;
-    }
-    // Fallback to regular rendering
-    return orig(tokens, idx, options, env, self);
-  };
-
-};

data/brutrb.com/.vitepress/theme/custom.css

@@ -1,14 +0,0 @@
-:root {
-  --vp-font-family-base: 'Helvetica Neue', 'Nimbus Sans', sans-serif;
-  --vp-font-family-mono: Courier, monospace;
-}
-.image-bg {
-  display: none;
-}
-td > code {
-  white-space: nowrap;
-}
-
-.VPHero img, .VPHome img {
-  border-radius: 0.5rem;
-}

data/brutrb.com/.vitepress/theme/index.js

@@ -1,18 +0,0 @@
-// https://vitepress.dev/guide/custom-theme
-import { h } from 'vue'
-import DefaultTheme from 'vitepress/theme-without-fonts'
-import './style.css'
-import './custom.css'
-
-/** @type {import('vitepress').Theme} */
-export default {
-  extends: DefaultTheme,
-  Layout: () => {
-    return h(DefaultTheme.Layout, null, {
-      // https://vitepress.dev/guide/extending-default-theme#layout-slots
-    })
-  },
-  enhanceApp({ app, router, siteData }) {
-    // ...
-  }
-}

data/brutrb.com/.vitepress/theme/style.css

@@ -1,139 +0,0 @@
-/**
- * Customize default theme styling by overriding CSS variables:
- * https://github.com/vuejs/vitepress/blob/main/src/client/theme-default/styles/vars.css
- */
-
-/**
- * Colors
- *
- * Each colors have exact same color scale system with 3 levels of solid
- * colors with different brightness, and 1 soft color.
- *
- * - `XXX-1`: The most solid color used mainly for colored text. It must
- *   satisfy the contrast ratio against when used on top of `XXX-soft`.
- *
- * - `XXX-2`: The color used mainly for hover state of the button.
- *
- * - `XXX-3`: The color for solid background, such as bg color of the button.
- *   It must satisfy the contrast ratio with pure white (#ffffff) text on
- *   top of it.
- *
- * - `XXX-soft`: The color used for subtle background such as custom container
- *   or badges. It must satisfy the contrast ratio when putting `XXX-1` colors
- *   on top of it.
- *
- *   The soft color must be semi transparent alpha channel. This is crucial
- *   because it allows adding multiple "soft" colors on top of each other
- *   to create a accent, such as when having inline code block inside
- *   custom containers.
- *
- * - `default`: The color used purely for subtle indication without any
- *   special meanings attached to it such as bg color for menu hover state.
- *
- * - `brand`: Used for primary brand colors, such as link text, button with
- *   brand theme, etc.
- *
- * - `tip`: Used to indicate useful information. The default theme uses the
- *   brand color for this by default.
- *
- * - `warning`: Used to indicate warning to the users. Used in custom
- *   container, badges, etc.
- *
- * - `danger`: Used to show error, or dangerous message to the users. Used
- *   in custom container, badges, etc.
- * -------------------------------------------------------------------------- */
-
-:root {
-  --vp-c-default-1: var(--vp-c-gray-1);
-  --vp-c-default-2: var(--vp-c-gray-2);
-  --vp-c-default-3: var(--vp-c-gray-3);
-  --vp-c-default-soft: var(--vp-c-gray-soft);
-
-  --vp-c-brand-1: var(--vp-c-indigo-1);
-  --vp-c-brand-2: var(--vp-c-indigo-2);
-  --vp-c-brand-3: var(--vp-c-indigo-3);
-  --vp-c-brand-soft: var(--vp-c-indigo-soft);
-
-  --vp-c-tip-1: var(--vp-c-brand-1);
-  --vp-c-tip-2: var(--vp-c-brand-2);
-  --vp-c-tip-3: var(--vp-c-brand-3);
-  --vp-c-tip-soft: var(--vp-c-brand-soft);
-
-  --vp-c-warning-1: var(--vp-c-yellow-1);
-  --vp-c-warning-2: var(--vp-c-yellow-2);
-  --vp-c-warning-3: var(--vp-c-yellow-3);
-  --vp-c-warning-soft: var(--vp-c-yellow-soft);
-
-  --vp-c-danger-1: var(--vp-c-red-1);
-  --vp-c-danger-2: var(--vp-c-red-2);
-  --vp-c-danger-3: var(--vp-c-red-3);
-  --vp-c-danger-soft: var(--vp-c-red-soft);
-}
-
-/**
- * Component: Button
- * -------------------------------------------------------------------------- */
-
-:root {
-  --vp-button-brand-border: transparent;
-  --vp-button-brand-text: var(--vp-c-white);
-  --vp-button-brand-bg: var(--vp-c-brand-3);
-  --vp-button-brand-hover-border: transparent;
-  --vp-button-brand-hover-text: var(--vp-c-white);
-  --vp-button-brand-hover-bg: var(--vp-c-brand-2);
-  --vp-button-brand-active-border: transparent;
-  --vp-button-brand-active-text: var(--vp-c-white);
-  --vp-button-brand-active-bg: var(--vp-c-brand-1);
-}
-
-/**
- * Component: Home
- * -------------------------------------------------------------------------- */
-
-:root {
-  --vp-home-hero-name-color: transparent;
-  --vp-home-hero-name-background: -webkit-linear-gradient(
-    120deg,
-    #333333 30%,
-    #d14141
-  );
-
-  --vp-home-hero-image-background-image: linear-gradient(
-    -45deg,
-    #ffe7e5 30%,
-    #a70c00
-  );
-  --vp-home-hero-image-filter: blur(44px);
-}
-
-@media (min-width: 640px) {
-  :root {
-    --vp-home-hero-image-filter: blur(56px);
-  }
-}
-
-@media (min-width: 960px) {
-  :root {
-    --vp-home-hero-image-filter: blur(68px);
-  }
-}
-
-/**
- * Component: Custom Block
- * -------------------------------------------------------------------------- */
-
-:root {
-  --vp-custom-block-tip-border: transparent;
-  --vp-custom-block-tip-text: var(--vp-c-text-1);
-  --vp-custom-block-tip-bg: var(--vp-c-brand-soft);
-  --vp-custom-block-tip-code-bg: var(--vp-c-brand-soft);
-}
-
-/**
- * Component: Algolia
- * -------------------------------------------------------------------------- */
-
-.DocSearch {
-  --docsearch-primary-color: var(--vp-c-brand-1) !important;
-}
-

data/brutrb.com/adrs.md

@@ -1,16 +0,0 @@
-# Architecture Decision Records
-
-The decisions here aren't *all* the architectural decisions I made, but are some of
-them, and mostly hold up.
-
-`adrs.cloud` is a Brut app.
-
-* [Rely on Web Standards and MDN Baseline](https://adrs.cloud/shared_adrs/padr_b6920f0df907886b8a9207e9e2c9c2a2)
-* [The Core Abstraction is the Plain Old Class](https://adrs.cloud/shared_adrs/padr_57f2397009a8aaf2c6083813ca588d73)
-* [Pages and Forms are First-Class Abstractions…not REST](https://adrs.cloud/shared_adrs/padr_cdfcbe6b116b80a4f3d53fb3a6ed44b2)
-* [Sequel will provide the data layer and its models will only model the database](https://adrs.cloud/shared_adrs/padr_01810ba90a92ec6c081a81affe212fb2)
-* [There will be no controllers. Purpose-built classes will support pages, forms, and components.](https://adrs.cloud/shared_adrs/padr_f318e74925cb3e9d7e0eda329d085c4a)
-* [Brut will not provider mailers, cloud storage, or background jobs](https://adrs.cloud/shared_adrs/padr_e7078d29f00710848ebbe43aea6094a6)
-* [Requiring files should not execute code](https://adrs.cloud/shared_adrs/padr_03b5cf8e34bb7900a38f6de27e50adaa)
-* [Phlex will be used for HTML templating](https://adrs.cloud/shared_adrs/padr_9529a5ada671254b5e5865b45abde92d)
-* [RSpec is the default testing framework](https://adrs.cloud/shared_adrs/padr_724a65340d734970ea222593a4a2760f)

data/brutrb.com/ai.md

@@ -1,68 +0,0 @@
-# AI Declaration and Notes
-
-LLMs and AI tools are a current fact of life.  We feel it's important to be realistic and up front about
-how they affect this project.
-
-## Levels of AI Use
-
-I created [declare-ai.org](https://declare-ai.org/) to allow precise documentation of how AI is used in a
-project. It defines four levels of AI use:
-
-1. No involvement at all.
-2. Non-create assistance, such as the completions GitHub Copilot may make while you are typing.
-3. Creative assistance, where an AI generated a large amount of code that you then modified. An example would be using a tool like Cursor to write code for your review.
-4. Completely Produced by an AI, for example if you used Stable Diffusion to create your icon.
-
-## Code
-
-The entirety of Brut's codebase could be grouped into three parts:
-
-* The library code developers use. This is, roughly, the code in `lib`, `brut-js/src`, and `brut-css/src`.
-* Tests of the library code.
-* Tools used to manage the library code, such as what's in `bin/`, `brut-js/bin`, `brut-css/bin`, etc.
-
-### Library Code Should Be Written By a Person
-
-We want the library code written by a person, i.e. it should have level 1 AI assistance: none.  As of this writing—June 17, 2025—all library code was written by a person.
-
-If some code is level 2—non-creative assistance—that is probably fine.
-
-### Tests Should Not Be Totally Written by AI
-
-As of this writing—June 17, 2025—the library has no automated tests.  The `adrs.cloud` app serves as the
-test suite.
-
-That said, as tests are developed, they must never be written entirely by an AI without human review (level 4).  Our preference is that all tests comply with level 1 or level 2, however we are open to creative assistance for tests as might be provided by a tool like Cursor.
-
-In any case, the author of a test should understand it and the maintainers must be able to understand and
-modify all tests without the use of AI tools.
-
-### Management Tools Should Not Be Totally Written by AI
-
-Like tests, management tools must be comprehensible by a person and the creator of the code must
-understand it.  That said, some of the tools were created with level 3 AI assistance, and we expect these
-tools may continue to be created this way.
-
-Nevertheless, this code must be reviewed and understood by a person.
-
-## Documentation
-
-We strive to have all documentation written by a real person.  None of this documentation, or the API
-documentation, is produced by a machine, although spelling and grammar corrections will certainly have been suggested by automated tools.
-
-We expect an LLM to be able to digest this documentation and source code and provide alternate analysis of how Brut works and how to use it.  We hope such analysis is correct and useful, however that cannot be guaranteed, so this documentation is the second best source of truth, the source code being the best.
-
-## Logos
-
-While the various logos look like someone typed "make me a logo in the style of the Washington, DC Metro", if you look closely, you will see the telltale sings that they were made by a person…a person who is not a professional designer.
-
-As such, these are all Level 1.
-
-## AI Information about Brut Should Be Viewed with Skepticism
-
-* **Answers from an LLM about Brut are likely incorrect.** LLMs will certainly not
-have been trained on information about Brut, since it is new.
-* **Code Completions of Brut Code are suspect.** I have observed that e.g. GitHub
-CoPilot is capable for properly completing Brut code if there is enough context, but
-it is not capable of, say, creating a component from scratch. **Review all Code
-Completions Carefully**.

data/brutrb.com/assets.md

@@ -1,131 +0,0 @@
-# Assets
-
-As mentioned in [Javascript](/javascript) and [CSS](/css), esbuild is used to bundle JavaScript and CSS. Brut also provides support for managing images.
-
-## JavaScript and CSS
-
-Both JavaScript and CSS are managed largely the same way: esbuild is given `app/src/front_end/js/index.js` or
-`app/src/front_end/css/index.css` and a bundle is produced.
-
-For both JS and CSS, the bundles are *hashed*, even in development.  This is to reduce differences in production
-and development.  The `asset_path` helper can translate the logical path (`/js/app.js` or `/css/styles.css`) into
-the specific hashed path.
-
-Sourcemaps are provided as well, for both development and production.
-
-### What is Hashing and Why Do It?
-
-In production, while your pages produce dynamic data, the CSS and JavaScript bundles themselves are not dynamic.
-They are the same for every single request until you change them. Because of this, it's common to configure a
-cache for these files. Often, that cache is a *content delivery network* or CDN.
-
-When a page is rendered, the browser will ask for the CSS and JS bundles. The CDN will tell the browser it's
-OK to cache the file, potentially for a very long time (years).  On subsequent requests for those files, the
-browser will re-use its cached copy, saving bandwidth and time.
-
-A downside of this approach is when you *do* want to change something.  While most CDNs allow you to invalidate
-their cached values, there are many layers of caching whose behavior can be hard to control.  It turns out to be
-much simpler to rename the file each you change it, thus "breaking the cache".
-
-A common way to do this is to create a hash of the file's contents and append that value to its name, so instead
-of `/static/css/styles.css`, the file would `/static/css/styles-98724fhjkjk.css`.  When you make a change to
-your CSS, it'll get new name, say `/static/css/styles-3yjgdrjksrfdws.css`.
-
-To keep you from having to deal with this directly, Brut's `asset_path` helper will translate a logical name like
-`/css/styles.css` to the actual name, like `/static/css/styles-3yjgdrjksrfdws.css`.
-
-### What are SourceMaps and Why Create Them?
-
-Bundled JavaScript and CSS will have been *minified*.  This means removing whitespace, line breaks and, in the
-case of JavaScript, potentially changing the actual names of classes and variables.  This is all to reduce the
-size of the file as much as possible without changing its meaning.
-
-In your browser's dev tools, all your CSS is one the first line of `styles.css` and every stack trace from your
-JavaScript is on line 1 of `app.js`.  This is not helpful for diagnosing issues.
-
-*SourceMaps* are separate files that translate the minified files back to normal ones, so you can see a normal
-stack trace with the actual line numbers of your source files.
-
-Brut's configuration of esbuild is to produce sourcemaps.
-
-## Fonts
-
-Custom fonts are managed implicitly by esbuild's managing of CSS.  In your CSS, you should reference fonts as
-relative to the CSS file.  For example, if you have the font `app/src/front_end/fonts/monaspace-xenon.ttf`, then
-your `app/src/front_end/css/index.css` should look like so:
-
-```css {3}
-@font-face {
-  font-family: "Monaspace Xenon";
-  src: url("../fonts/monaspace-xenon.ttf") format("truetype");
-  font-display: swap;
-}
-```
-When CSS is bundled, esbuild will copy and hash the fonts, then rewrite the CSS to reference them.
-
-Brut does not support font management in any other way.
-
-## Images
-
-Brut supports managing images, and will `rsync` them from `app/src/front_end/images` to
-`app/public/static/images`, where you can reference them via `/static/images/«image_name»`.
-
-Brut does not support hashing of image names.
-
-You can reference images like so:
-
-```ruby
-def view_template
-  div do
-    # Renders app/src/front_end/images/foo.png
-    img src: "/static/images/foo.png", alt: "Picture of a foo"
-  end
-end
-```
-
-## SVGs
-
-You can place `.svg` files in `app/src/front_end/images` if you wish to use them in `<img>` tags.  However, if
-you place svgs in `app/src/front_end/svgs`, they can be inlined into your HTML via `inline_svg`, provided by `Brut::FrontEnd::Component::Helpers` and included in all components and pages.  In this case,
-there is no need for a build step, since the SVG source is included directly in your HTML. This works well
-for icons.
-
-## `favicon.ico`
-
-`Brut::FrontEnd::Middlewares::Favicon` is configured by default to handle requests for `/favicon.ico`.  It
-returns a 301 to `/static/images/favicon.ico`. This means that Brut expects
-`app/src/front_end/images/favicon.ico` to exist.
-
-
-## All Other Assets
-
-Brut currently does not support any other managed asset. However, you can place files in `app/public/static` and
-they will be served up directly.
-
-
-## Technical Notes
-
-> [!IMPORTANT]
-> Technical Notes are for deeper understanding and debugging. While we will try to keep them up-to-date with changes to Brut's
-> internals, the source code is always more correct.
-
-_Last Updated May 7, 2025_
-
-`bin/build-assets` manages all of the behavior described on this page.  `bin/build-assets css` and
-`bin/build-assets js` modify the file `app/config/asset_metadata.json`, which stores the mappings between logic
-paths and hashed paths:
-
-```json
-{
-  "asset_metadata": {
-    ".js": {
-      "/js/app.js": "/js/app-7MMIZXTZ.js"
-    },
-    ".css": {
-      "/css/styles.css":"/css/styles-ZAISBLGE.css"
-    }
-  }
-}
-```
-
-As you can see, this format could support multiple bundles and additional file types.

data/brutrb.com/bin/build

@@ -1,5 +0,0 @@
-#!/bin/bash
-
-set -e
-
-npm run docs:build

data/brutrb.com/bin/deploy

@@ -1,7 +0,0 @@
-#!/bin/bash
-
-set -e
-
-bin/build
-rsync -av --delete .vitepress/dist/ ../docs/
-echo "brutrb.com" > ../docs/CNAME

data/brutrb.com/bin/dev

@@ -1,5 +0,0 @@
-#!/bin/bash
-
-set -e
-
-npm run docs:dev

data/brutrb.com/bin/setup

@@ -1,6 +0,0 @@
-#!/bin/bash
-
-set -e
-
-echo "[ brutrb.com/bin/setup ] Setting up BrutJS"
-npm install