pkmn.cc/dmg
Out of date (december 2018)
large departure (automatic formatter, more aggressive restructuring etc)
Better to build same repo (dont disrupt forks, maintain ‘brand’, avoid developers having to download 2 repos)
Don’t put set logic in @psim/dmg
Typechecking JSON! (irrelevant, shave that yak with @psim/data instead)
Step 1 = webpack + module!



Separate model vs. view code (refactor view code later...)
= Testable
Typescript = better maintainability/robustness, con: adds build step
Can it be done piecemeal? Typed JS? One file at a time?
Interoperability (Leftovers again etc, EPOke chrome tooltip plugin)
(stretch) load async (sets/other gen mechanics)

Generation order vs. backwards generation order?

import/export sets from @psim/data
 get all data from @psim/data
 mismatch of data from psim (pkmunge)
 use toID instead


Parser logic (embedded in server)
State from client (params vs base64 encoded)
Use statistics from smogon instead of manual sets (display better)
Better mobile client support (collapse more boxes - hide things you rarely need to change)

Share damage logic with PS? (PS doesnt expose rolls, would need to be restructured dramatically, less efficient)