ecowden / pluto-path Goto Github PK

Should be good with ecowden/pluto.js#30. Let's add some tests before we consider it done, though...

Update dependencies, linting, etc.

Mimic ecowden/pluto.js#23.

Every now and then I find I want some extra control over injection. For instance, I may have a factory function that creates a class, so I name it's file upper case; or the filename isn't a legal JavaScript argument name. It would be nice to be able to override the default guessing behavior.

Maybe something like:

// Badly-Named-Class-Factory.js

module.exports = function factory(injectMe) {
  return class SomeClass {
    // ...
  }
}

module.exports.$plutoConfig = {
  strategy: 'factory', // treat this as a factory function
  name: 'SomeClass' // change the name of the binding
}

Note: this is a really dumb example, don't actually write code like this.

One of the top complaints is that errors, expecially SyntaxErrors, can get swamped in pluto's error handling stacks. Ideally, those errors should propagate directly, making it easier for developers, and especially new developers, to identify issues.

I'd like to be able to selectively load (or not load) specific source files.

For instance, if my source tree includes tests, I would like to exclude files that match the glob, **/*Spec.js.

Not so much a requirement as an inevitability.

We will almost certainly want to replace require-all to satisfy other requirements, especially #2. When we do, we should consider using async calls, which will in turn impact this module's API.

Consider yourself warned!

First priority!