First of all, great job on this package! It helps a lot with installing dependencies in TypeScript projects and the CLI output is really pretty.
However, I've found one small problem which is that when you don't specify a name in your project's package.json, the CLI output shows undefined:
If you're wondering why anyone would not specify a package name: It's simply redundant for "top-level packages" like back- or front-end codebases since they are not meant to be used as package dependencies.
My PR makes the package name fall back to the directory name which is helpful enough in most cases:
Coverage remained the same at 100.0% when pulling 89b2562fc78133f4eda1824f5cd76fb20622952f on shroudedcode:package-name-fallback into 3952f8eb6345f28f8210249ce21f96181cd6fce7 on jeffijoe:master.
Coverage remained the same at 100.0% when pulling 89b2562fc78133f4eda1824f5cd76fb20622952f on shroudedcode:package-name-fallback into 3952f8eb6345f28f8210249ce21f96181cd6fce7 on jeffijoe:master.
First of all, great job on this package! It helps a lot with installing dependencies in TypeScript projects and the CLI output is really pretty.
However, I've found one small problem which is that when you don't specify a
name
in your project'spackage.json
, the CLI output showsundefined
: If you're wondering why anyone would not specify a package name: It's simply redundant for "top-level packages" like back- or front-end codebases since they are not meant to be used as package dependencies.My PR makes the package name fall back to the directory name which is helpful enough in most cases: