Seems like this would be better off as YAML...
Groups:
ATeam:
- [FirstName, LastName, Height]
- [Joe, Soap, 184]
- [Mary, Ryan, 169]
- [Alex, Dole, 174]
I just can't get past the type mismatch for useState with an array...
const temperatureStatePair = useState(23);
const temperature = temperatureState[0];
const setTemp = temperatureState[1];
23 is not an array.
That's understandable... I actually kind of appreciated the use of HTTP(S) references for code with Deno.. though a repository is nice enough. The x.deno.land worked, but JSR is definitely a better longer term solution, and really happy to see decent npm support.
Thinking about a minor rewrite of a couple modules this weekend to be JSR first, adding enough for an npm publish to remain working.
I like a lot of what JSR offers, I do hope that it sees a fair amount of uptick. I've been using Deno a lot more than Node lately, mostly in that it's better for shell scripting with a shebang and direct imports compared to package.json and node_modules etc.
I'd like to see a few things get refactored to work better over time, but who knows.
As much as I dislike Windows, and even in Windows will prefer WSL... Windows development is still a thing and I try to be friendly to Windows developers as much as reasonable.
That's why Concurrently exists even if there's Bash on Mac, Linux, BSD, etc.
Seems like this would be better off as YAML... Groups: ATeam: - [FirstName, LastName, Height] - [Joe, Soap, 184] - [Mary, Ryan, 169] - [Alex, Dole, 174]I just can't get past the type mismatch for useState with an array... const temperatureStatePair = useState(23); const temperature = temperatureState[0]; const setTemp = temperatureState[1]; 23 is not an array.