Saving some custom options to a local .npmrc file automatically

[zkochan]

There are some npm/pnpm configs that change the way the node_modules is built.

• ignore-scripts
• no-optional
• no-bin-links
• global-style (not used by pnpm)
• legacy-bundling (not used by pnpm)

and some pnpm-specific ones might get introduced. Like copying instead of hard linking and changing the way leaf dependencies are linked to node_modules.

I suggest in order to have consistent installs for every developer, to automatically add or update an .npmrc file in the root of the package, with values of such configs (if their value is not the default)

[wmertens]

I wonder though if it is ok for pnpm-specific options to live in .npmrc (it's not called .pnpmprc after all). Other projects simply use package.json.

[zkochan]

It is a complex problem. I would also like a separate config but that would mean additional fs operations. We should read npm configs in any case because pnpm tends to be a drop-in replacement that works with existing configs.

…

On Fri, Mar 30, 2018, 13:03 Wout Mertens ***@***.***> wrote: I wonder though if it is ok for pnpm-specific options to live in .npmrc (it's not called .pnpmprc after all). Other projects simply use package.json. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#820 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB1pm0BpjW2zdksmhZChHwmXb5zlnfNaks5tjgLZgaJpZM4OBiEy> .

[wmertens]

well, generally, pnpm is already writing to package.json when installing deps… as a start, the key "pnpm" could be read at least? On Fri, Mar 30, 2018, 12:44 PM Zoltan Kochan, <[email protected]> wrote:

…

It is a complex problem. I would also like a separate config but that would mean additional fs operations. We should read npm configs in any case because pnpm tends to be a drop-in replacement that works with existing configs. On Fri, Mar 30, 2018, 13:03 Wout Mertens ***@***.***> wrote: > I wonder though if it is ok for pnpm-specific options to live in .npmrc > (it's not called .pnpmprc after all). Other projects simply use > package.json. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#820 (comment)>, or mute > the thread > < https://github.com/notifications/unsubscribe-auth/AB1pm0BpjW2zdksmhZChHwmXb5zlnfNaks5tjgLZgaJpZM4OBiEy > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#820 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADWljPc2DTxUSeuQZ5sQZ_wn5Ldc0cFks5tjgyVgaJpZM4OBiEy> .