ecosystem CI tests

[jbolda]

Motivation

To assist in confirming that the built assets run downstream after publishing, we want to test this in CI against the examples repo.

Approach

• write a setup script that can be run locally and in CI
• add a workflow that will execute the build and/or tests in the example repo
• add tests to the example repo (see React Testing Library Example starfx-examples#5)
• dynamically fetch branch -- use matching branch from starfx-examples if it exists, see below

Dynamic Branch

Additionally, we added a script that will dynamically pull a branch from the examples repo. If the branch name in the current PR running the workflow matches a branch name in the examples repo, it will pull that instead of the main branch. This is to assist in dealing with breaking changes. A PR here and a PR there would allow stepping each forward with a green build.

Screenshots

Branch by default

Branch when a match exists

[jbolda]

We ended up switching to an npm install.

new Deno.Command("npm", {
      args: ["add", "starfx@file:../../starfx/npm", "--install-links"])

The examples were originally intended to be npm based, and parcel was having trouble with the symlink and additional node_modules. It appeared to be resolving up the tree in this repo.

@parcel/core: Failed to resolve 'react-dom' from 

'/home/runner/work/starfx/starfx/starfx/npm/node_modules/react-redux/es/utils/reactBatchedUpdates.js'
  /home/runner/work/starfx/starfx/starfx/npm/node_modules/react-redux/es/utils/reactBatchedUpdates.js:1:41
  > 1 | export { unstable_batchedUpdates } from 'react-dom';
  >   |                                         ^^^^^^^^^^^
@parcel/resolver-default: Cannot find module 'react-dom'

I left the symlink option in the script as it may be useful in the future for other repos.

[neurosnap]

.scripts/ -> scripts/

[neurosnap]

Thanks so much for all your help, this is great!