Closed tommueller closed 7 years ago
Can I see your package.json
as a Gist or something?
Also looks this & #59 may be similar issues
Thanks! This will help! Scoped packages weren't originally supported, so it's "natural" that they failed. There are some considerations that need to be made to support them...
In your package.json
, did you manually change the entrypoint values (main
, es2015
, module
) and typings
values? Just wondering, it doesn't seem like librarian would've produced those values.
In your package.json, did you manually change the entrypoint values (main, es2015, module) and typings values? Just wondering, it doesn't seem like librarian would've produced those values.
I renamed them for pasting them to remove the company name. They are originally in the form "./package-name.es5.js
etc. pp.
Ah, gotchya
By the way, I'm going to close this one and use #59 as the main issue (only because I looked at it first).
PS: thanks for all the great work and latest updates. Have been on holidays for the last weeks and am super excited that this is so actively maintained!
I just realized I didn't say thank you for your kind words...so thank you!
My build is failing since the update to the official beta versions, because apparently the new build-process reads the package-name from the package.json for something? When I created the package I called it
MyLib
and some weeks later had to rename it to@MyCompany/MyLib
. Since the upgrade this breaks the build process.also running
ngl init
again and trying to rename the module here does not work.I get the same error if I change the package name to anything else!
PS: thanks for all the great work and latest updates. Have been on holidays for the last weeks and am super excited that this is so actively maintained!