James Messinger

@big-r81 - ok, thanks for the analysis. Looks like this isn't going to be as straightforward as I had hoped. :-/

If you want to dereference _all_ references (not just external ones), then use the `--dereference` option in Swagger CLI (or the [`dereference()` method](https://github.com/BigstickCarpet/swagger-parser/blob/master/docs/swagger-parser.md#dereferenceapi-options-callback) in Swagger Parser)

That's the point of the `bundle` command. It only dereferences external references. But it sounds like that's not sufficient for AWS API Gateway, so you'll have to fully dereference everything...

Can you double-check the full file path in the error message, to make sure it's correct. My guess is that some part of the path is missing or misspelled. ```...

Ok. Now I see what you're talking about. And you're right, the file paths have nothing to do with it. **The bad news:** This is, in fact, a bug **The...

I'm pretty sure I already know where the bug is, and it shouldn't be hard to fix at all. That said... my schedule is **super busy** right now, so I...

Sure! I'd certainly appreciate your help. I'm pretty sure the bug is in the `crawl()` method in [`resolve.js`](https://github.com/BigstickCarpet/json-schema-ref-parser/blob/master/lib/resolve.js#L51-L83)

This error means that you have an invalid `$ref` somewhere in your schema. Without actually seeing your schema, I can't get any more specific than that.

I intend to support inline references in the next version of JSON Schema $Ref Parser, which I have already begun working on. 👍 In the meantime, I will implement @n1ywb's...

I just published version 3.3.1, which includes the stopgap fix that @n1ywb suggested