One package per task flow

[dangunter]

I think it would be better to use the JavaScript packaging to create one package per task flow, with a common package for the shared elements. My understanding is that recent npm can handle loading packages from a local file so the layout could be something like

src/
  shared/
    Shared (core, base, pick your term) npm package here
  task-flows/
     examine-items/
       - npm package here
     compare-items/
       - npm package here
     search-dataset/
       - npm package here
     contribute-data/
       - npm package here
     run-optimization/
       - npm package here
     monitor-tasks/
       - npm package here

Then the npm package.json in the task-flows packages could refer to the package at "../shared". Perhaps there are technical packaging reasons this makes no sense, but StackOverflow implied it was reasonable?

Also encapsulated in this example is the idea of a naming convention for the packages, e.g., "verb-noun". With as few verbs and nouns as possible to get consistency. (This is, I must confess, inspired by the Microsoft Powershell command names)