If you've been working on javascript or related framework projects then definitely you came across the file named package.json and we might be curi...
For further actions, you may consider blocking this person and/or reporting abuse
Good article @naveenchandar . well explained each options with example. recent days one option added in package.json. This option also useful for now a days.
Example:
More info
Yeah but this is available only on Yarn right?. Correct me if I'm wrong.
Yes. I guess now a days most of the people using yarn only.
I Forgot to add this note: This option only useful for who using yarn package manager in their project.
small addition, a lot of people don't know about the
publishConfig
key, you can use it to set theaccess
and other variables so you can avoid doing thenpm publish --access=public
when working with scoped packages.Might help someone.
That's a great one to add ๐.
The "homepage" property is used for a completely different purpose for projects using react-scripts. This is a bit frustrating, in my opinion.
Also, if your package is distributing both commonjs and ES modules, the "main" property should be the path to the commonjs module, and the "module" property should be the path to the ES module.
Agreed ๐.
@naveenchandar : its best article, I did found any course which explain the package.json like you. Now I have clear understanding of package.json thanks Naveen
Thanks a lot. ๐
Thanks for sharing
Pleasure..๐
Thanks mate..I was not aware of fixpack earlier. Glad to know.๐
Nice article.
Thank you ๐.
Nice article but please change the title ๐
๐.. I'm bad at creating title. Can you suggest me some good one ?๐
Some Titles :
Depends on content of this article:
Setting it to private doesn't stop it being published. Unless you're only working on public packages.
Great article man, Thank you very much!
Thank you ๐
Nice article ๐. This article revised all my concepts.
Thank you..๐