James M. Greene

It would be awesome if FMF could target specific commits. e.g. https://5minfork.com/zeroclipboard/ZeroClipboard/commit/e6e75f3e85147a2b21789aaf59b23e12c5ff8133 Thoughts? I'd also be fine with it if I had to manually specify the branch/tree that the commit...

Accept BLANKET_CONFIG env var for alternate config file path

5

A BLANKET_CONFIG file will contain ONLY the JSON that is normally accessed from a 'package.json' file's 'config.blanket' object For example, in "package.json": ``` json { "config": { "blanket": { "pattern":...

Implement `.far()`

1

Implement an experimental function called `.far()` for finding the farthest (most shallow) `script` element for the current execution call stack.

``` json { "license": "MIT" } ```

Use 3rd party `Error#stack` parser instead of homegrown parser

3

StackTrace.js has extracted its internal stack parser as ["error-stack-parser"](https://github.com/stacktracejs/error-stack-parser), with 1 dependency on ["stackframe"](https://github.com/stacktracejs/stackframe) (a simple internal data model to represent frames in the call stack). Make both `devDependencies`, then...

Attempt to improve locating of correct inline scripts via function source code

2

**Critical Piece:** Being able to get the function reference to the calling function, e.g. via `_nearestExecutingScript.caller`/`arguments.callee.caller`/`arguments.caller`. Seems like `"use strict"` (JS strict mode) usage will make this next to impossible/useless....

Per @ollym's request on JamesMGreene/document.currentScript#9: > It would be helpful if you could list the techniques you're using for script detection in english. The source code structure makes it difficult...

Implement an experimental function called `.origin()` for finding the originating `script` _or attribute node_ (e.g. `onclick`) for the current execution call stack.

e.g. for Chrome: https://code.google.com/p/v8-wiki/wiki/JavaScriptStackTraceApi#Appendix:_Stack_trace_format There are some special cases, e.g. location when a function was created via `eval`, is native, cannot be located, etc.

It looks like the references to the `CONFIGS_WITH_METHODS` variable were removed way back in `v158` but the definition is still present. [Compare `v157`..`v158`](https://github.com/github/pages-gem/compare/v157..v158#diff-577aa6cfe09866693f9c87c4aff83d66df2a9ebe56deda981315348142119af3)