Does it make sense to have a "serve" command that can start up a static web server for the directory?

Probably means shipping something like node-static or some other lib. Are licenses compatible? There is a pretty easy python one-liner floating around, maybe just suggest using that instead.

This doesn't happen every time, but often enough.

When running volo add on travis-ci with node 0.8.22, I often get the message ERROR: Error: Unable to find end of central directory record

See https://travis-ci.org/iceddev/frozen/jobs/6893229 for an example.

I have tried modifying my repo in many ways to solve this problem but it seems to be a problem with the zip files. Not sure if something in volo is changing them or the Github API has changed or is being flakey.

I have an application folder structure looking like:

-package.json -app.js -node_modules -www --js ---require.js ---jquery.js

If I am in the "www/js" folder and use "volo add", it creates a new package.json in the www/js folder.

Ideally, volo could check down all the folders until it finds the first package.json. If that package.json references the current folder as a baseUrl, it could use that package.json to ammend to?

When creating a library with several modules (and one main module), it feels strange having to keep all the source files at the root directory. I would prefer the following structure where all javascript source files are in a subdirectory rather than at the root of the project.

  # The repo of the lib
  lib
      main.js
      helper.js
  tests
      main_test.js
  buster.js
  README
  volofile

When doing volo add mylib I would like to install the lib in the following way

# A project consuming mylib
lib
    mylib
        main.js
        helper.js
    mylib.js # adapter

This would allow doing

require("mylib");
require("mylib/helper");

Currently I would have to do

require("mylib");
require("mylib/lib/helper");

which makes reusing the submodules of mylib more difficult.

I wonder how I should go about this. To sum up, currently the options are

1. Keep all source files in the root file as recommended in the wiki.
2. Keep all source files in a subfolder, but then submodules of the library become difficult to reuse
3. Keep all source files in a subfolder and after volo adding, create add paths: { "mylib": "lib/mylib/lib" } to the config which is not as nice as having everything working out of the box.

Right now version conflicts are handled by "first one encountered wins", which is fine enough for small projects. However, it would be nicer if the full dependency tree is scanned, and then if there is a version conflict, ask the user which one they want to install.

Say I want to use chosen.js in my project. If I do "volo add chosen" (and if there is an override package.json configured in volo repo), then volo will only install a single javascript file and remove everything else. I would like to preserve the images and css files and @import them in my main.css file of the project. I'm not sure what happens if you then include a library (with css file) that uses a library (with css file) that uses chosen and imports it's css. Do those css imports still resolve correctly. What css files do I now include in my toplevel project. On one hand it feels that this might be better left completely separate from the javascript stuff, but on the other hand it would be nice that when I update to the latest chosen.js version, the css and images are kept up to date as well.

Work it out. Some things in particular:

• Right now tar -z and rm are used via child_process. How does that work in Windows? Show zip files be used instead? Is there a reliable zip utility that can be used in Node, something that is not a binary component that needs to be built to ship volo?
• How would symlinks work?

HI, I had a problem to run volo after installing nodejs and volo on my ubuntu gnome shell distr :

/usr/bin/env: node: No such file or directory

/usr/bin/env: node: Aucun fichier ou dossier de ce type

It was hard to find how to fix so I put it here. I had to

apt-get install nodejs-legacy

ERROR: Error: Download failed, HTTP code: 301:

If I specify the dependency as:

http://github.mycompany.com/project/foo/raw/master/foo.js

Depending on how things are configured, you may be redirected to:

https://github.mycompany.com/project/foo/raw/master/foo.js (notice the https)

Volo treats this 301 redirect as an error.

One can work around this by updating the URL; however, I wouldn't expect a 301 to cause an error.

I've got a project with 16 dependencies and each repo download takes about 8 seconds to complete (I'm in South Africa, we're not renowned for our fast internet connections). What's interesting is that when I load the URLs directly in the browser, it only takes me about 2 seconds to load that same URL. I know Volo needs to do a repo search and could also be checking the amd-repo list, but I'm still not entirely sure how that is all filling up 8 seconds. Just wondering if there's any scope for speed improvements, because I think it's an important factor for adoption as well.

It's sometimes very hard to figure out what's wrong with a volofile, and the ability to hook up a debugger like node-inspector would be immensely useful. However, adding --debug or --debug-brk when running volo seems to do nothing.

Is there a way to do this currently, that I'm unaware of?

There are small typos in:

• tests/commands/create/support/addOnCreate/js/jquery.js
• tests/doh/_browserRunner.js

Fixes:

• Should read insignificant rather than insignifant.
• Should read amenable rather than ammenable.

Semi-automated pull request generated by https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Bumps shell-quote from 0.0.1 to 1.7.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

I recently had an issue during our build process, volo was getting stuck on:

volo add -f -nostamp jquery/qunit/v1.14.0#. <-- Endless loop, eventually exceeds rate_limit

Realized that it's making tons of requests, blowing through my rate limit within a minute or so. The fix ended up being jquery --> qunitjs.

volo add -f -nostamp qunitjs/qunit/v1.14.0#. <-- This works fine, 1 request

But I was wondering if it's a bug that it doesn't recognize that the Url is broken, or if there is an option for limiting the number of requests before it will move on/throw error.

Looks like AWS wants something fancier done for downloading files from them.

Test:

volo add https://github.com/gaye/dav/releases/download/v1.0.3/dav.zip#dav.js

<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AuthorizationQueryParametersError</Code><Message>Query-string authentication version 4 requires the X-Amz-Algorithm, X-Amz-Credential, X-Amz-Signature, X-Amz-Date, X-Amz-SignedHeaders, and X-Amz-Expires parameters.</Message>
<RequestId>80D47BFAAC204179</RequestId>
<HostId>0HariKX8ScYk17bnjlLAZNTy3qgstjggzWTYpkh2zxYuudRhBKxn+fBCE7z/bkTFc7B9H94tD/s=</HostId>
</Error>

Trying to use curl for the same action also gets the same error.

To reproduce, run:

volo add -amd https://ajax.googleapis.com/ajax/libs/angularjs/1.3.0-rc.3/angular.js depends=jquery=jQuery exports=angular

Contents of package.json:

{
  "volo": {
    "dependencies": {
      "angular": "https://ajax.googleapis.com/ajax/libs/angularjs/1.3.0-rc.3/angular.js"
    }
  }
}

Expected behaviour:

rm angular.js
volo install
# angular.js should be amdified

Thanks for the great tool that is volo!

As opposed to excludes, the opposite. npm has a files which allows only keeping explicit files, in a nested directory search, which is a bit different than a pure opposite of volo.excludes, which only goes by top level entries. Marking for 0.3.2, but may get pushed for semver reasons, if 0.3.2 does not turn into an 0.4.0.