changes in webpack.config for issue #22 | tsconfig with explanatory comments,

[Udayraj123]

Resolves #22

Some analysis:

Build timings checks

Command used -

time npm run build

Then (with react-scripts and other bloatware) (refer total)

1. npm run build  58.57s user 5.48s system 168% cpu 37.973 total
2. npm run build  29.30s user 3.31s system 212% cpu 15.333 total
3. npm run build  28.26s user 3.27s system 210% cpu 14.986 total

Now (with manual webpack config)

1. npm run build  24.79s user 1.67s system 155% cpu 17.068 total
2. npm run build  19.99s user 1.93s system 157% cpu 13.929 total
3. npm run build  18.73s user 1.57s system 162% cpu 12.522 total

Dev timings checks

Although not so reliable, mentioning this just as part of an experiment

Command used (with ^C just after Compiled Successfully message)-

time npm run start

Then

1. npm run start  0.32s user 0.11s system 4% cpu 10.030 total
2. npm run start  0.31s user 0.10s system 4% cpu 8.994 total
3. npm run start  0.26s user 0.09s system 4% cpu 8.080 total

Now

1. npm run start  17.46s user 1.74s system 149% cpu 12.852 total
2. npm run start  17.26s user 1.71s system 157% cpu 12.021 total
3. npm run start  17.37s user 1.71s system 153% cpu 12.410 total

The ~3 second increase in first compile is most likely due to the fact that it now also compiles vmmx-schema (temporarily #22)