Closed RaoOfPhysics closed 2 weeks ago
Rescoping this task to “npm library” (because at that point it becomes moot what the contents of this repo include).
Hi @ColinC-UoE, some notes for today:
deploy-npm
part of this task merged to develop
. I guess that means changing if: github.ref == ‘refs/heads/creating-NPM-library’
to use release
(although when testing you’ll need to switch it back locally). Merge develop
again into your branch and do a PR on your branch in GitHub. Hi @ColinC-UoE. Looks like you closed this but haven’t yet merged to develop
– it looks like there are some conflicts, so probably best to fix those, do the merge and only then mark the task as done.
fluid-lang
package.json
to publish to NPMpackage.json
yarn add fluid-lang
into a fresh Node projectyarn add @explorable-viz/fluid
and thenyarn install
release
onlybuild.yml
anddeploy.yml
build
triggers onworkflow_call
deploy
triggers onpush
; publish to NPM ifbuild
succeeds, and pushes to GitHub if publish to NPM succeedsSee also:
1057
1018
Right now, to make a Fluid publication, we have to clone the whole
explorable-viz/fluid
repo and then create HTML files and more within it. We would like to move to a modular approach where the development of the language is decoupled from publication mechanisms.For now, we will set up separate repos for generated documents (starting with a minimal HTML page etc.). GitHub Actions will be used to build the website associated with each independent repo, using the HTML file.
To use
fluid
, at the moment will have to usegit submodule
. And we will need to have a.purs
file with all the Fluid modules and data for analysis in addition to the HTML+CSS files. Eventually these will be migrated as follows:git submodule
for Fluid →npm
package for Fluid..purs
file specifying Fluid modules and analysis data →.yml
file with this information.—
Related to https://github.com/explorable-viz/fluid-examples/discussions/10