Question: Say I have this scenario. 3 Libraries - 1) Orders 2) Suppliers 3) Containers

In the Orders I can choose "Supplier" and "Container" which are look up fields, looking into the 'Title' column of the "Suppliers" and "Containers" libraries, respectively. 

Now Let's say in Order X, I choose supplier: SupplierA.

I want to only be able to choose containers of that supplier. 

Possible starting points: 

a) In the Containers' library I have a look up field "Supplier" looking into the same Suppliers library, so the logic would be, show all the containers which have the same RelatedSupplier. 

or

b) The name 'SupplierA' always appears within the Title of the container, so the logic would be, show all the containers where the Title contains the name of the supplier.

What would be the best way to achieve this? Javascript would probably need to be used unless there is a SharePoint way that I don't know about. I would appreciate a starting point.

I am working in a SharePoint Online environment.

Answer: 
I'm trying to diagnose what is happening here.

As a possible workaround, can you run
npm outdated

and in your package.json file update the @microsoft/# references? They should all be 1.1.0, and probably include sp-build-web, sp-core-library, sp-module-interfaces, sp-webpart-base and sp-webpart-workbench.

OK - sorted out the problem with running the original yeoman generator with the latest bits. The problem is that there was a package published with a patch version change (1.0.0 -> 1.0.1) that should have been 1.1.0. The 1.0.1 package references 1.1.0 packages (which are part of the latest release). So we wind up with a mismatched collection of packages. We're working on getting this sorted out and we will republish our packages. People using the 1.0.x yeoman generator won't need to do anything other recreate the solution (or reinstall the npm packages) if they hit this issue.

Last Update - fix has been released. Offending packages have been removed, updated packages published.
Ran into this issue yesterday, but the issue seems resolved after reinstalling my packages today. I'm using the 1.0.0 packages.