Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Frank Ebersoll
@frankebersoll
even more, it needs to be relative
or absolute to your workstation root
that's another problem that would be solved by an additional publish-build
Blake Niemyjski
@niemyjski
relative would be best
Frank Ebersoll
@frankebersoll
during debugging, we need source maps that support our local file structure
Blake Niemyjski
@niemyjski
yeah
Frank Ebersoll
@frankebersoll
after publishing, we need to support loading via the web
that might be two different things.
i'm back on master now, finishing stringily.
stringify*
Blake Niemyjski
@niemyjski
kk
Frank Ebersoll
@frankebersoll
ah, another thing!
the new npm seems to deduplicate modules into the root node_modules directory, wherever possible
Blake Niemyjski
@niemyjski
yeah
Frank Ebersoll
@frankebersoll
i guess it does this by downloading the "lowest common denominator" version of a module that is used by other modules
Blake Niemyjski
@niemyjski
it seems much slower tho
there is a github issue for that
Frank Ebersoll
@frankebersoll
i like this behavior, but I would guess it has problems with our current package.json
as we specify versions explicitly, it has to use that exact version
Blake Niemyjski
@niemyjski
yeah
I do that because I’ve been burned by newer packages
plus the build should never change ever
it should know the specific packages
Frank Ebersoll
@frankebersoll
maybe it has more possibilities for optimization if we use ^version, as the default does
Blake Niemyjski
@niemyjski
yeah
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*
Frank Ebersoll
@frankebersoll
i understand
i really don't know about the implications
Blake Niemyjski
@niemyjski
yeah me either
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
Frank Ebersoll
@frankebersoll
i guess we're pretty close to being full stack developers
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.
Frank Ebersoll
@frankebersoll
they "fixed" it with Thread.Sleep
sigh sorry.
Blake Niemyjski
@niemyjski
back talking to sander :)
lol
Frank Ebersoll
@frankebersoll
?
Blake Niemyjski
@niemyjski
it’s all good
was in a tab and forgot about the main channel /sorry
Frank Ebersoll
@frankebersoll
tell me if i'm ranting too much :-) might happen occasionally