Coder Social home page Coder Social logo

bebop's Introduction

bebop NPM version Build Status Gitter chat

Jazzy build tool for sophisticated front-end development.

Bebop is a rapid web development tool with a built-in http server, preprocessing workflow support and intelligent browser reloading, freeing you to hit the keys like an undead techno-zombie Charlie Parker.

Installation

$ npm install -g bebop-cli

If you use bebop's static file serving feature it will automatically inject the Javascript required. If you want to enable something similar for your own connec/express apps you can use bebop.middleware, or link directly to bebop-client/bebop.js.

Usage

Change to the directory in which your application resides and run bebop.

$ cd ~/myapp
$ bebop

CLI

› bebop --help
bebop [options] [file]

Options:
  --compile, -c   Compile files and exit
  --compilers,    Specify compiler to use for a given extension
  --config,       Specify bebop.coffee to use
  --exclude, -x   Exclude files for watching, compiling
  --force-reload  Force reload when file is compiled
  --host, -h      Hostname to bind to
  --include, -i   Include files for watching, compiling
  --no-compile    Do not compile files automatically
  --no-server     Do not run static file server
  --no-watch      Do not watch files for changes
  --open, -o      Open browser automatically
  --port, -p      Port to listen on
  --pre           Command to execute first
  --secure, -s    Require authentication
  --static-dir    Directory used as root for static file server
  --work-dir      Directory used as root for compiling, watching

  --help          Display this message
  --version, -v   Display version

Configuration

You can configure Bebop by creating a .bebop file in either your home directory or the root of your project. If you use an extension of .coffee it will be imported as a coffeescript module. Properties exported in this module will be used to override the defaults used.

Example .bebop configuration file

fs        = require 'fs'
path      = require 'path'
requisite = require 'requisite'

module.exports =
  port: 3000

  compilers:
    jade: (src) ->
      # only compile index.jade file
      if /index.jade$/.test src
        "jade --pretty #{src} --out #{path.dirname src}"

    # use requisite to bundle client-side coffee script files
    coffee: (src, dst, cb) ->
      requisite.bundle {entry: src}, (err, bundle) ->
        return cb err if err?

        fs.writeFileSync dst, bundle.toString()
        cb null, true

Editor integration

Integration with vim is provided by vim-bebop. You can do all sorts of fancy stuff like evaluate Javascript, Coffeescript, get completions, etc.

bebop's People

Contributors

greenkeeper[bot] avatar greenkeeperio-bot avatar zeekay avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

bebop's Issues

An in-range update of sake-cli is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.5.25 of sake-cli was just published.

Branch Build failing 🚨
Dependency sake-cli
Current Version 0.5.24
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

sake-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 4 commits.

  • d6346c4 0.5.25
  • 51329f6 Update sake-bundle
  • bffb51c Update deps
  • d423df2 Update yargs, coffeescript, sake-outdated, find-coffee, sake-core, sake-bundle

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of marked is breaking the build 🚨

The dependency marked was updated from 0.6.2 to 0.6.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

marked is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 0.6.3

Fixes

Docs

  • add docs for workers #1432
  • Add security policy #1492
  • Update supported spec versions #1491
  • Update test folder descriptions #1506

DevOps

  • Use latest commit for demo master #1457
  • Update tests to commonmark 0.29 #1465
  • Update tests to GFM 0.29 #1470
  • Fix commonmark spec 57 and 40 (headings) #1475
Commits

The new version differs by 87 commits.

  • 124c576 Release v0.6.3 (#1508)
  • 570af73 0.6.3
  • 1ce85ca update test descriptions in CONTRIBUTING.md (#1506)
  • a265632 🗜️ minify [skip ci]
  • c95667f Fix breaks (#1507)
  • e774f77 fix breaks
  • da4d967 add test
  • c86d242 update test descriptions in CONTRIBUTING.md
  • 0b7fc5e 🗜️ minify [skip ci]
  • 5ba9ba5 Merge pull request #1497 from UziTech/revert-1464
  • 9c91e40 revert #1464
  • 396591a Merge pull request #1491 from markedjs/docs-spec-versions
  • 5c6a039 Merge pull request #1492 from markedjs/security-policy
  • 508da4d add links
  • 9182f80 Add security policy

There are 87 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of source-map-support is breaking the build 🚨

The dependency source-map-support was updated from 0.5.12 to 0.5.13.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

source-map-support is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 4 commits.

  • 4a9c45d 0.5.13
  • c4453fd Update built files
  • bfc73f9 Merge pull request #249 from evanw/LinusU-patch-1
  • 4852362 Tweak regex in retrieveSourceMapURL

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of ws is breaking the build 🚨

The dependency ws was updated from 7.0.0 to 7.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ws is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 9 commits.

  • 38d3bf2 [dist] 7.0.1
  • a0af764 [test] Use the correct value for the Content-Length header
  • b086179 [fix] Allow to disable sending the SNI extension (#1587)
  • e9e8ba5 [pkg] Update eslint-config-prettier to version 5.0.0 (#1588)
  • 36ef757 [doc] Add missing dependency in code snippet (#1581)
  • 911bb6f [minor] Fix typo in JSDoc comment (#1565)
  • 8050d5f [lint] Enable quotes rule
  • 995c527 [test] Enable --throw-deprecation
  • fbc077b [test] Do not use the deprecated outgoingMessage._headers property

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of utf-8-validate is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.0.1 of utf-8-validate was just published.

Branch Build failing 🚨
Dependency utf-8-validate
Current Version 4.0.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

utf-8-validate is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 12 commits.

  • e7e007c [dist] 4.0.1
  • 3c2009d fix(package): update nan to version 2.10.0 (#65)
  • 4ccaa4b fix(package): update nan to version 2.9.1 (#64)
  • d997dbc chore(package): update prebuild to version 7.4.0 (#63)
  • 9dc3872 chore(package): update prebuild to version 7.3.0 (#62)
  • c44a32b fix(package): update prebuild-install to version 2.5.0 (#61)
  • a11d80b chore(package): update prebuild to version 7.2.0 (#60)
  • 7d0257d chore(package): update mocha to version 5.0.0 (#59)
  • e6cd9e7 chore(package): update prebuild to version 7.1.0 (#58)
  • 1756207 chore(package): update mocha to version 4.1.0 (#57)
  • bdda52f chore(package): update prebuild to version 7.0.0 (#56)
  • baf72c8 fix(package): update prebuild-install to version 2.4.0 (#55)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of http-errors is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.6.3 of http-errors was just published.

Branch Build failing 🚨
Dependency http-errors
Current Version 1.6.2
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

http-errors is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 20 commits.

There are 20 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of connect is breaking the build 🚨

The dependency connect was updated from 3.6.6 to 3.6.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

connect is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 45 commits.

There are 45 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of colors is breaking the build 🚨

The dependency colors was updated from 1.3.3 to 1.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

colors is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 8 commits.

  • baa0e1c update roadmap
  • 56de9f0 Add bright/light colors, closes #128
  • b4d964b Make stylize() work for non-ASCI styles (#155)
  • a1407ae Document colors.enable() and .disable() (#255)
  • acb7f66 Merge branch 'develop' of github.com:Marak/colors.js into develop
  • 9bfb136 more node versions
  • 5d9eb90 Fixed: throws non-intuitive error on color.red(null) but not on colors.red(undefined) (#261)
  • aa012aa Redo weak equality check so we can colorize null in safe mode (#257)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of morgan is breaking the build 🚨


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The dependency morgan was updated from 1.9.1 to 1.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

morgan is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 1.10.0
  • Add :total-time token
  • Fix trailing space in colored status code for dev format
  • deps: basic-auth@~2.0.1
  • deps: depd@~2.0.0
    • Replace internal eval usage with Function constructor
    • Use instance methods on process to check for listeners
  • deps: on-headers@~1.0.2
    • Fix res.writeHead patch missing return value
Commits

The new version differs by 79 commits.

There are 79 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of ws is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 5.1.1 of ws was just published.

Branch Build failing 🚨
Dependency ws
Current Version 5.1.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

ws is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 5.1.1

Bug fixes

Commits

The new version differs by 5 commits.

  • 10c92ff [dist] 5.1.1
  • f335d79 [fix] Add default value for servername option (#1347)
  • 2d7bf88 [perf] Use js version of {un,}mask() for very small frames (#1348)
  • f52debe [doc] Explain the behavior of server.close() more precisely (#1342)
  • 83ce534 chore(package): update eslint-plugin-import to version 2.10.0 (#1340)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

how to exclude directories?

my ~/.bebop.coffee looks like:

module.exports =
  exclude: ["build", "old"]
  compilers:
    css: (src) ->
      "postcss -u autoprefixer -u rucksack-css #{src} -d build/"

it gaks with the exclude line in there. How do I specify directories and files to exclude?

Cannot find module '../lib/cli'

after sudo npm install -g bebop, I run bebop and get:

module.js:340
    throw err;
          ^
Error: Cannot find module '../lib/cli'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/usr/lib/node_modules/bebop/bin/bebop:2:1)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)

An in-range update of bufferutil is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 3.0.4 of bufferutil was just published.

Branch Build failing 🚨
Dependency bufferutil
Current Version 3.0.3
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

bufferutil is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 13 commits.

  • 34580b7 [dist] 3.0.4
  • e4a8450 fix(package): update nan to version 2.10.0 (#94)
  • 0aa18f2 fix(package): update nan to version 2.9.1 (#92)
  • 58a03a7 chore(package): update prebuild to version 7.4.0 (#91)
  • 7b47314 chore(package): update prebuild to version 7.3.0 (#90)
  • bd27a20 fix(package): update prebuild-install to version 2.5.0 (#89)
  • 9111105 chore(package): update prebuild to version 7.2.0 (#88)
  • b6899d2 chore(package): update mocha to version 5.0.0 (#87)
  • 7074094 chore(package): update prebuild to version 7.1.0 (#86)
  • 740f461 chore(package): update mocha to version 4.1.0 (#85)
  • 8e746ea chore(package): update prebuild to version 7.0.0 (#83)
  • f0f913b fix(package): update prebuild-install to version 2.4.0 (#82)
  • a549e11 fix(package): update nan to version 2.8.0 (#80)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of sake-test is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.1.6 of sake-test was just published.

Branch Build failing 🚨
Dependency sake-test
Current Version 0.1.5
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

sake-test is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits.

  • c544e7a 0.1.6
  • fb42362 Update coffeescript, sake-bundle, sake-cli
  • b5556cc Migrate to coffeescript package
  • 318534e Update sake-bundle, sake-cli
  • 53bfa07 Update coffee-script, sake-bundle, sake-cli, sake-outdated, sake-publish, sake-version
  • 2e01ff6 Update gitignore

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of serve-static is breaking the build 🚨

The dependency serve-static was updated from 1.13.2 to 1.14.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

serve-static is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 1.14.0
Commits

The new version differs by 37 commits.

There are 37 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of sake-bundle is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.6.6 of sake-bundle was just published.

Branch Build failing 🚨
Dependency sake-bundle
Current Version 0.6.5
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

sake-bundle is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of http-errors is breaking the build 🚨

The dependency http-errors was updated from 1.7.2 to 1.7.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

http-errors is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 18 commits.

There are 18 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of coffeescript is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.2.4 of coffeescript was just published.

Branch Build failing 🚨
Dependency coffeescript
Current Version 2.2.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

coffeescript is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 5 commits.

  • e5aa758 2.2.4 (#5025)
  • 001f97a Fix #5013: return statement as an expression (#5014)
  • ce66a49 Make node --harmony bin/cake test pass on Node 9 (#5012)
  • 0268505 Optimize 'for-range-by' loop when 'by' is literal number (#5016)
  • 5a43b2d simplified test file skipping (#4996) (#5003)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

example using bebop as middleware?

Are there any examples of using bebop as middleware for an express4 app?
I'd like to inject bebop functionality into an existing app.

websocket error

I'm getting:

bebop.min.js:668 WebSocket connection to 'ws://192.168.1.68:1987/_bebop' failed: Connection closed before receiving a handshake response

when viewing a bebop site. any ideas?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.