Not sure if its going to make any difference on the stats.json, but should we focus the efforts on webpack or webpack2?
If we get it right, even if the stats.json changes, we should only need to change the parser to gather the data from the new format
There is no difference in the stats currently. If there will be, it's propably good to support both formats.
Not many people here, right? I think it will be better to support both versions of webpack if there will be any changes soon in json structure.
hey all. excited to help out on this
hello everybody, really excited to join this team!
Hi, so excited for this tool.
hey everyone, looking forward to working together
Greetings everyone, excited to help and make this great tool even greater
Hello everyone! I've created an issue with the feature list (mostly citing @sokra) - add your ideas to it too.
Hi. @sokra , what is our next plan of actions. This started great, hope we can push it further with the same enthusiasm. Do you need any help in that?
I can start to bootstrap an application or to do whatever is useful at our current stage.
I've put together a plan here: webpack/analyse-tool#3 You can summarize the feature list in the wiki, or start bootstraping the basic infrastructure.
Feel free to tweak the plan. Everybody should be able to edit it.
i'm trying to use the analyse tool. when i upload my "stats.json" that was generated from my build, i'm getting all sorts of parsing errors. i'm on a windows machine. my path to my angular 2 project is something like c:\users\tim\visual studio\some more spaces\theproject\stats.json. how can i generate the stats.json without getting this parsing error at upload?