v0.4.1

Fix a bug with regex used for parsing yarn.lock. (@NavneetKaur0111)

The previous version of the regex incorrectly looked for exact package names preceded by any character which resulted in false matches (e.g. [email protected] matched @types/[email protected]). This resulted in a crash when assuming that npmjs.com API would contain the date for a non-existent version of the package. Now the regex requires that the package name be preceded by a space, a quote, or be placed at the very beginning of the line.