mikedewar@tomstafford text!
(it's more readable and less fun in the readme)
Tom Stafford@mikedewar nice. Although now it doesn't build on my machine (did some installs, got entangled in dependency hell. Maybe I'll come back to it in the morning)
@tomstafford npm is a huge jump in complexity for these things at least for me. I understand it so little that I'm not entirely sure even where to start. Try `npm install --save-dev webpack` and then `npm run build`. Might work! Might not though eh? These js people are just making stuff up as they go along; it's glorious and tiring.
@mikedewar i solved some of my dependency issues and then got a new error. The SO replies for the possible causes makes me think that js is a wild wild west - just the range things and types of things which might cause this issue https://stackoverflow.com/questions/43037590/field-browser-doesnt-contain-a-valid-alias-configuration
@tomstafford so I think, in retrospect, you should not have to be building this thing; I fear I’m just not shipping the result of the build, which I should be. Will investigate tomorrow!
@tomstafford hey so I just pushed a load of code that is much better (arguably) than the code I had, but the actual viz has taken several steps back until i finish my refactor. One thing though is that I pushed the "compiled" code so it lives in /dist. I'd be super curious if you served up the repo as normal and then visited localhost:8888/dist (replace 8888 with your port) do you at least get some little squares?
@mikedewar not sure about localhost, but if i just open the .html file in a browser it works