Makes Dredd a monorepo

[artem-zakharchenko]

🚀 Why this change?

• To manage Dredd and friends more effectively

📝 Related issues and Pull Requests

• A part of Future Dredd proposal #1186

✅ What didn't I forget?

• To write docs
• To write tests
• To put Conventional Changelog prefixes in front of all my commits and run npm run lint

[artem-zakharchenko]

Current state: Managing docs, moved to the root directory, fixing references to fixtures from hooks/index.rst. There were some issues with docutils python dependency being not installed. Should be solved with moving docs to the root.

[kylef]

I don't think this comment is about the PR itself, but once we have dredd-transactions in the repo too, we will want to alter the smoke tests to test with the in-repo dredd-transactions.

When the time comes for this, you can take a look at how I solved similiar in API Elements where "Fury CLI" uses the local in-repo libraries as part of the smoke test: https://github.com/apiaryio/api-elements.js/blob/dbd6aafbd50fcb2fab43eae9d612561147308377/.circleci/smoke.sh

[pksunkara]

LGTM.

[artem-zakharchenko]

@honzajavorek please note that this pull request also brings Yarn as the default package manager to Dredd. The reasoning is the support for "workspaces", which grants an ability to properly install shared dependencies between multiple packages in a monorepo.

Due to that, I'd also update the docs (mainly contributing guidelines) to mention the Yarn preference. What do you think?

[honzajavorek]

@artem-zakharchenko

Yarn as the default package manager to Dredd

For development, right? So we're talking about the "internals" page in the docs. Sure, reasonable.

For Dredd users we should still recommend npm.

[artem-zakharchenko]

Yes, of course. Publicly nothing changes, Yarn is preferred for contributing only, not to fix package managers during dependencies management and CI. Well, in that case you're right, nothing to update (except of contributing docs in a separate pull request).

[honzajavorek]

[artem-zakharchenko]

Experiencing a flaky test (#1519). Re-running the workflow...