firstandthird / parse-dir Goto Github PK

View Code? Open in Web Editor NEW

1.0 5.0 2.0 139 KB

Node lib to recursively read the files in a directory and return their contents

License: MIT License

JavaScript 98.67% CoffeeScript 0.81% LiveScript 0.47% Mustache 0.05%

parse-dir's Introduction

parse-dir

=========

Node lib to recursively read the files in a directory and return their contents.

Installation

npm install parse-dir

Usage

parseDir(glob, callback);

Or, if you prefer to make it synchronous:

var result = parseDir(glob);
var otherResult = parseDir.sync(otherGlob);

Example

var parseDir = require('parse-dir');

parseDir('*', function(err, files) {

});

Output

[
  {
    fullpath: '/path/to/file.ext',
    filename: 'file.ext',
    basename: 'file',
    extension: '.ext',
    raw: 'raw contents of file',
    contents: 'parsed contents of file',
    parsed: true|false //if file is supported, it will parse the contents.  If false, contents == raw.  See Parsing Files.
  }
]

Parsing Files

If parseDir knows how to parse a file, it will attempt to read it and turn it into a javascript object.

Supported Files

YAML
JSON
JS
CoffeeScript
Livescript

parse-dir's People

Contributors

Watchers

Forkers

antonio-laguna isabella232

parse-dir's Issues

An in-range update of js-yaml is breaking the build 🚨

Version 3.8.0 of js-yaml just got published.

Branch	Build failing 🚨
Dependency	js-yaml
Current Version	3.7.0
Type	dependency

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

As js-yaml is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

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

Commits

The new version differs by 8 commits .

dddcb5f 3.8.0 released
686fa0b Merge pull request #327 from SmartBear/master
9bd2c10 Report "duplicated mapping key" errors at start of block
1918a7f fix formatting of the example
ee14eab clarify usage of style option
f6bafed Support node 6.+ Buffer API when available
d37ec86 Deps bump (eslint, esprima)
1497178 Travis: update tested node.js versions to 4, 6 & 7

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of coffee-script is breaking the build 🚨

Version 1.12.3 of coffee-script just got published.

Branch	Build failing 🚨
Dependency	coffee-script
Current Version	1.12.2
Type	devDependency

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

As coffee-script is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

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

Commits

The new version differs by 23 commits .

635e207 Update release date for 1.12.3
e87d574 Merge pull request #4429 from GeoffreyBooth/1.12.3
b89dd04 Add other 1.12.3 updates to changelog
8ce7c30 Update generated docs for 1.12.3
45d0a7d Update browser compiler for 1.12.3
7291277 Bump version
6d27277 Update documentation for 1.12.3.
3108244 Fix stack trace (#4428)
d0ed2de Merge pull request #4420 from GeoffreyBooth/backport-2-doc-changes
a61429c Updated output
fbdfa65 Apply SVG fill color through CSS
02198eb Fix link to Try CoffeeScript
cd8be89 Trim the installation and usage sections; can backport to v1
b398c88 Fix releaseHeader for the initial release; should backport to v1
f4353fa Merge pull request #4417 from BrianRossmajer/patch-1

There are 23 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

doesn't throw error if fails to parse

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.