Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 06:50
    alvin-su commented #472
  • 03:15
    fengrui358 starred exceptionless/Exceptionless
  • Dec 15 14:07
    niemyjski commented #472
  • Dec 15 07:50
    alvin-su opened #472
  • Dec 15 01:35
    niemyjski synchronize #452
  • Dec 15 01:35

    niemyjski on elastic7

    Only put consumes attribute on … (compare)

  • Dec 14 16:39
    ejsmith synchronize #452
  • Dec 14 16:39

    ejsmith on elastic7

    Log the correct task id and cat… (compare)

  • Dec 14 06:25
    ejsmith synchronize #452
  • Dec 14 06:25

    ejsmith on elastic7

    Minor (compare)

  • Dec 14 06:00
    ejsmith synchronize #452
  • Dec 14 06:00

    ejsmith on elastic7

    Add missing task id (compare)

  • Dec 13 22:43
    ejsmith synchronize #452
  • Dec 13 22:43

    ejsmith on elastic7

    More reindex job changes (compare)

  • Dec 13 15:46
    ejsmith synchronize #452
  • Dec 13 15:46

    ejsmith on elastic7

    Just retry 3 times (compare)

  • Dec 13 15:44
    ejsmith synchronize #452
  • Dec 13 15:44

    ejsmith on elastic7

    More log message changes (compare)

  • Dec 13 14:25
    niemyjski synchronize #452
  • Dec 13 14:25

    niemyjski on elastic7

    Added retry reindex for disconn… (compare)

Blake Niemyjski
@niemyjski
well
Frank Ebersoll
@frankebersoll
i already got that working, just not yet in our project
Blake Niemyjski
@niemyjski
they would be pointing to dist/temp and our breakpoints are set in /
I think that’s the issue
Frank Ebersoll
@frankebersoll
they need to point back to the actual sources
ehm....
exceptionless-spec.js.map contains only source code, no mappings
not cool.
Blake Niemyjski
@niemyjski
{"version":3,"file":"submitSync.js","sourceRoot":"/source/","sources":["submitSync.ts"],
that sourceroot should be /src/ no?
Frank Ebersoll
@frankebersoll
right.
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 :-)