smartprocure / directory-metagen Goto Github PK

While the documentation is pretty good, there are a few things we could add to improve it. This thread will keep track of those things.

• Provide a more detailed version of example output for the different formats

• Clarify potential questions regarding ES2015 (Is it a requirement? etc.)

• Flesh out the example with Gulp at the end

• Fix dependency tag, broken link

In case where there's an external javascript with the same name as a folder in the same root, the correct way to approach this with the current way directory-metagen works is by making the external javascript file to be within the folder with it's same name, but renamed as index.js

This information should be better explained in the README.md

Version 3.5.0 of bluebird just got published.

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

As bluebird 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 💪

Your Greenkeeper Bot 🌴

{
    path: __dirname + '/public/react-components/babel-src/reports/apps',
    output: '__reportCatalog.js',
    format: es6Format,
    exclusions: [
        '__reportCatalog.js'
    ]
}

In the above scenario the output ends up being apps__reportCatalog.js file located in the reports folder. The desired result is a file named __reportCatalog.js located in the apps folder.

I have a situation where I'd like to generate a file deep within a directory tree that searches the parent, grandparent, etc directories.

like:

a/
  b1/
  b2/
  b3/
    c1/
       all_from_b123.js

I tried to achieve this with something like metagen assets/javascripts/dashboard_2 commonJS a/b3/c1/app_from_b123.js --filter="../../examples.js" but it didn't work. I tried various combinations of the command. Is this something the tool supports? Thank you!

Version 3.4.0 of mocha just got published.

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

As mocha 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 💪

Your Greenkeeper Bot 🌴

Hello,

I've been toying around with metagen but can't get it to work - it always outputs an empty file. My hunch is that somehow I am not putting the path correctly - running from CLI it throws out a "folder not found" error, and running from package.json the same command runs but generates an empty file.

I think it would help a lot if the README would include more info on how the path is processed (relative to script directory ? relative to current folder ? absolute?)

Standard provides an API which might allow us to format all the output code with standard by default (we'll make sure we provide an optional parameter with the formatting function, so users can use their own). However, standard uses the file system API in their lintText and lintTextSync functions, which makes our unit tests fail, since we need to mock the fs API.

I opened an issue in the standard repo asking if we could optionally disallow lintText and lintTextSync to interact with the file system api: standard/standard#904

Let's see what happens!

I'm thinking this could look a bit better if we used es6+'s features, however, the output would be very limiting afterward (but it will still work for our use cases).