or absolute to your workstation root
that's another problem that would be solved by an additional publish-build
that might be two different things.
i'm back on master now, finishing stringily.
stringify*
the new npm seems to deduplicate modules into the root node_modules directory, wherever possible
there is a github issue for that
as we specify versions explicitly, it has to use that exact version
I do that because I’ve been burned by newer packages
plus the build should never change ever
it should know the specific packages
thought about that
guess we’d know when we are building that as we are commiting the files manually
we don’t do it for our spa app because we auto deploy and need to know the changes immediately
need to know that nothing ever gets updated and deployed without us changing it*
i really don't know about the implications
kinda funny..
it’s impossible to be a fullstack developer and that term.. because there are a trillion of things that you need to know the nitty gritty details of and it’s impossible
how many things do we use every day that we have a gist of how it works or a good understanding
but knowing the implications is hard without serious work for something trivial
I’ve been spending a lot of free time to read up on things I don’t know and I still feel 10yr behind
i have seen different :-)
both of us know what we don't know and actually think about it. i have seen too many people doing things while having absolutely no clue whatsoever
and they can't even be blamed, because everybody started like this
but they were writing business critical applications and trying to tell me that they don't synchronize their code because, c'mon, this race condition will only happen in one of a hundred times.
sigh sorry.
lol
was in a tab and forgot about the main channel /sorry