So since this is turning into a build system....

There is a tool in here for extracting imports.

Concept

// can we move import to require w/ transpilation, slowly // can cjs be imported in browser and node if it's named properly? // or is it just a node thing? // lets try all situations // but there are also rules about who THEY import (create things that export, that's the start, create things that import, and then things in between, and run time tests! // parameterize...... try except can work for cjs, not gonna work for the other tone, gonna have to be a bunch of separate files, or modifiable files. and we still have to create a bunch of exports. gotta do it for both. // and that's not a question of what the bundlers can do. if we're importing something we mean to be async but is not, we can wrap it all.

1. Take entry files
2. Move the AST
3. Develop dependency tree
4. Lint
5. Mark files by year of javascript
6. Mark files my module type
7. Mark files if acceptable for web or not
8. ANALYZE -- You can show a graph visualization here -- You should be able to run specific operations on graph filters/sections of graph -- Graph can probably be transformed based on directory structure/depth
9. Transform type of javascript
10. Transform type of import/export or bundle

Why can't we just follow the errors? Try to import index.js with firefox and take it all the way through, through every fucking file.

TODO

• fix build
• fix source maps
• better interface for webpack?
• plotly (fix documentation on refactor)
• Get cytoscape running with DAGRE
  • Get exports working on heap
  • Fix package.json
  • Get tests working on heap
  • See if import works
  • See if require works
  • Make fork
  • Make pull request
  • Make issue on cytoscape (explain)
  • Document the import tool, document the changes to both cytoscape and
  • fix dagre
    • convert all to import (lib, dist, src, test)
    • make sure everything is pointing to .js
    • get babel installed
    • do some babel conversion
    • change linter
    • change package.json
    • make commit on graph
    • add information about babel
    • submit pull request draft for graph
    • fix babel named default
    • parar express
    • review my prs and such
    • read
    • do the same thing for dagre
      • get it cloned
      • do the basic renaming
      • do the change of all imports to exports
      • change the makefile (add convert)
      • see if it loads with graph lib
        • fix import export stuff
      • see how transpile handles the require (it should be fine)
      • do the package.json
    • do the same thing for dagre-cytoscape
      • analyzing....
      • test the html tests
      • are there tests? (no)
      • see if we can change the dagre dependency and pass the tests (or do the html test)
      • create seperate folders
      • do conversion, probably in package.json is fine
        • can source even be convered???
        • see what happens if we try to get it from node
        • gotta link my repo
        • we don't know if it will import correctly because it uses new javascript and doesn't transpile down.
        • are constants supposed to be modifiable
        • can we import any bundled versions from web?
        • debug
          • look at old html and make sure you didn't get rid of anything
          • review webpack
          • try all combinations
          • look at source conversion and compared to old
          • document what happens
          • try this plugin with one, then without the other
          • try this plugin with just preset env according to docs
      • separate babel config for compile
      • html example (depends on node?)
      • package.json converter is fine, no need for make
      • 5t rollup working
      • lint config probably needs to be changed
      • do package.json export require/import
      • go through readme and release stuff
      • submit
  • email laura
  • Fix up units on VSH/POROSITY
    • Fix bugs
      • colorwheel
      • what to do about recursion 20:25
      • Push
    • Separate matrix into matrix range
  • Get pull on lasio
  • submit pull request on cytoscape to roll everything into non-min
    • test to make sure it works without other imports
  • publish what you wrote to ajpikul or what
  • if dagre gets submitted, see if you still need a special loader
  • migration (check again)
  • derma (make list of options)
  • Package (call them or talk to them)
• How is plotly using browserfy
• TODO in slack for neyberson, as opposed to Trello, add notes that you have in notebook
• Fixup cytoscape in json-browser- as in, figure out what versions you're going to use and how you're going to use them.
• make coffee
• try to log in to western union again
• try to attach your account and send urself money
• see about western union
• get milk
• do derma
• Let's redo the toolbar
  • It needs to be better organized, it needs to be better compartmentalized
    • Tabs for windows (separate toolbar for apps?, and command window, and console)
    • Some kind of toolbar app (maybe try a model on key capture)
    • Into modules you can initialized
    • Make it work
    • better defaults for namespaces
• Talk to Thomas
• Let's keep going with webpack- turn webpack reader into into report Class please
• Let's get the reports pretty printed
• Let's get notified in track? I have no idea what that meant
• Let's lint what we've done in json browser
• Get cytoscape making trees/looping/sorting (Graph should be tree)
• Let's create that tree of all the files
• Let's get it styled properly (color coded depth, shape based on type of import, name is folder)
• Let's be able to aggregate statistics into folders (ie collapsable)
• Let's get relationships shown on hover
• Let's be able to select between types of relationships shown
• Let's be able to add filters to what's shown, in a queue type structure
• Create a dictionary of file sizes
• Add to plotly unidades and multiple lines, add to pozo better checking for types
• Do some operations on index.js
• npm install --web or something like that to make an import map

-- Health- are there types we didn't check for (make sure nothing is under the table) -- Do we have all modules, do all modules have a relationship -- What happens if we chunk -- Diff Trees ? -- Serialize Trees ? -- Get Our Own Resolver ?

Errata

I'm only using ESM,

I had to submit a request to heap to update for ESM, but I'm using it locally right now.

I'm using a slightly modified version of cytoscape to make the actual pulls easier.

there is a "modified" folder with // CHANGE markers.