On Wed, Nov 30, 2016 at 1:48 AM, Tom Fennelly <tom.fenne...@gmail.com> wrote:
> I'm just wondering what might be the risks associated with manipulating the
> contents of the node_modules folder outside the normal "npm install" etc
> commands. IOW ... are there reasons why the a raw "drop in" of packages into
> the node_modules is a bad idea Vs doing it through the normal "npm install"
> I have a colleague proposing this basic idea as a solution to a problem we
> have (longer story that probably doesn't need airing here). For me, it just
> feels like the wrong thing to do (scares me), but my "gut feeling" is not a
> good enough reason for me to say that I think we should not consider doing
> So, I'd love if someone could enlighten me to the potential dangers, or if
> there's no real danger and nothing to worry about.
> Thanks guys.
In the end it's just files on disk. If your node_modules has the
expected layout, node doesn't care if it was you or npm that put the
Job board: http://jobs.nodejs.org/
New group rules:
Old group rules:
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.