pact-js vs. pact-node

[basickarl]

What is the difference between the pact-js, pact-node and pact-web packages?

We have the following types of code:

• asynchronous
• synchronous
• node.js
• browser
• isomorphic

Which package should one choose if doing one of the following in my list?

[mefellows]

TL;DR - you want Pact JS in most instances.

• asynchronous - Pact JS
• synchronous - Pact JS
• node.js - Pact JS
• browser - If you actually need it to run in the browser (almost always debateable), Pact Web
• isomorphic - If you actually need it to run in the browser (almost always debateable), Pact Web

The "I need to run it in the browser" question comes up occasionally. The question is this - for your JS code to be able to make a call to another API, is this dependent on browser-specific code? In most cases, people use tools like React/Angular which have libraries that work on the server and client side, in which case, these tests don't need to run in a browser.

I think this table is a good one, and I'm going to use it as a starting point to publish onto the various repositories to make things clearer.

See also pact-foundation/pact-js-core#145.

This from the Pact Node github home page:

Does this answer your question?

[basickarl]

@mefellows Perfect! Thank you very muchos!

[mefellows]

You're welcome. I've just added a first cut at a table. Not sure it's in the right place but it's a start.