James Messinger

Yeah, that's a bug that [has been fixed](https://github.com/BigstickCarpet/json-schema-ref-parser/commit/32510a38a29723fb24f56d30f055e7358acdd935) in the latest version of `json-schema-ref-parser`, but there are some breaking changes, so Swagger Parser [hasn't been updated yet](https://github.com/BigstickCarpet/swagger-parser/issues/30).

Swagger Parser v4.0 _beta_ is now available, and includes the fix for this issue. You can install the beta using `npm install swagger-parser@beta`. - [v4.0 code branch](https://github.com/BigstickCarpet/swagger-parser/tree/releases/4.0.0) - [v4.0 documentation](https://github.com/BigstickCarpet/swagger-parser/tree/releases/4.0.0/docs)...

Actually... I think the expected behavior that you described should be the default. No need for a new option. Just need to fix the circular-dereferencing logic.

Copying my DM'ed response here... > Just read your comments. Not sure how to fix it off-hand. Will require some experimenting. > > One option might be to drop support...

Without seeing your actual schema, I can't say for sure what's causing the error. But it sounds like you have an invalid JSON Pointer in there somewhere. The `resolve()` method...

Swagger Parser actually uses [json-schema-ref-parser](https://github.com/BigstickCarpet/json-schema-ref-parser#json-schema-ref-parser) under the hood, which is a spec-compliant implementation of [JSON Reference](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03) and [JSON Pointer](https://tools.ietf.org/html/rfc6901). I don't want to introduce non-spec-compliant behavior into that library (which...

I can definitely see this being useful, but probably not something that should be built-in. We plan to add full-featured plugin support at some point, and this kind of functionality...

This error is coming from your browser, not from Swagger Parser. If you check the developer console, I suspect you'll see an error message like this one: That's a CORS...

I'm going to leave this issue open and mark it as an "enhancement". I'll see if there's a way to add code to Swagger Parser to detect CORS errors and...

@dpmartin990 - Check your browser console for errors. You may need to enable CORS on your server