Thanks for this sample, it hit the spot. However, It seems like the npm published packages @ryancavanaugh/pkg2 and @ryancavanaugh/pkg3 are not up-to-date with the latest checked-in package.json files. @ryancavanaugh/pkg1 seems OK.
Simple example from command line:
PS C:\> npm info @ryancavanaugh/pkg1 main
lib/index.js
PS C:\> npm info @ryancavanaugh/pkg2 main
index.js
PS C:\>
Expected: the main file for pkg2 should read lib/index.js, like pkg1.
I don't understand why this is inconstant, clearly the checked in pkg2/package.json has the lib/ prefix on it's main entry. However the lack of the proper entry causes code trying to use pkg2 or pkg3 to fail at runtime.
Thanks for this sample, it hit the spot. However, It seems like the npm published packages @ryancavanaugh/pkg2 and @ryancavanaugh/pkg3 are not up-to-date with the latest checked-in package.json files. @ryancavanaugh/pkg1 seems OK.
Simple example from command line:
Expected: the main file for pkg2 should read
lib/index.js, like pkg1.I don't understand why this is inconstant, clearly the checked in pkg2/package.json has the
lib/prefix on it'smainentry. However the lack of the proper entry causes code trying to use pkg2 or pkg3 to fail at runtime.