Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 04 14:34

    mrjoelkemp on master

    Fix package name to not conflict 3.7.4 (compare)

  • Feb 04 14:34

    mrjoelkemp on v3.7.4

    (compare)

  • Feb 04 14:31

    mrjoelkemp on master

    3.7.3 (compare)

  • Feb 04 14:31

    mrjoelkemp on v3.7.3

    (compare)

  • Feb 04 14:31

    mrjoelkemp on master

    Fix package name to lowercase (compare)

  • Mar 09 2018 11:34

    mrjoelkemp on master

    3.7.2 (compare)

  • Mar 09 2018 11:34

    mrjoelkemp on v3.7.2

    (compare)

  • Mar 09 2018 11:33

    mrjoelkemp on bump

    (compare)

  • Mar 09 2018 11:33
    mrjoelkemp closed #240
  • Mar 09 2018 11:29
    mrjoelkemp synchronize #240
  • Mar 09 2018 11:29

    mrjoelkemp on bump

    Use node-prune (compare)

  • Mar 09 2018 11:16
    mrjoelkemp opened #240
  • Sep 03 2017 19:29

    mrjoelkemp on master

    3.7.1 (compare)

  • Sep 03 2017 19:29

    mrjoelkemp on v3.7.1

    (compare)

  • Sep 03 2017 19:28

    mrjoelkemp on bump

    (compare)

  • Sep 03 2017 19:28
    mrjoelkemp closed #239
  • Sep 03 2017 19:25
    mrjoelkemp opened #239
  • Sep 10 2016 19:51

    mrjoelkemp on v3.7.0

    (compare)

  • Sep 10 2016 19:51

    mrjoelkemp on master

    3.7.0 (compare)

  • Sep 10 2016 19:50

    mrjoelkemp on more_jump_to

    (compare)

David Kebler
@dkebler
Joel, I've been using Atom exclusively now for awhile and am getting better at writing node. Atom is now much more stable. I've got some current projects on my plate but would like to eventually take a stab at a fork of dependents for Atom since I am really missing it.
Andreas Schoeller
@Asc2011
hi joel, dependants looks great - is there any chance to use it with uncompiled CS(coffee-script) ?
ƇʘƁ̆ąƇ́
@anchnk
hello, are linux OSes supported out of the box within dependents ?
for some reason dependents can't find my node's path i put the root directory of my nvm's node installation in my user config file
ƇʘƁ̆ąƇ́
@anchnk
this is my User settings for the package "node_path": "/home/tvba5179/Documents/Build/git/public/nvm/versions/node/v6.9.2/bin/node"
$ which node /home/tvba5179/Documents/Build/git/public/nvm/versions/node/v6.9.2/bin/node
Gilad Shoham
@GiladShoham

Hi, Joel, nice to e-meet you.
I want to add a new feature to all of your dependents repos.
It is kind of a tree shaking, but not exactly.
Let's say I have the following file structure
src/myFile.js
src/utils/isString.js
src/utils/isBoolean.js
src/utils/index.js

The index in the utils folder is only import everything from the utils folder and just export it.
So in myFile.js i can do something like:
import { isString } from './utils';
(without referring to the actual file, in this case isString.js)

This will create a dependency tree like this:
myFile.js -> index.js -> (isString.js, isBoolean.js)

but actually, myFile is not importing anything from isBoolean so it's not a real dependency.

This pattern is very popular, and the index files may contain a lot of dependencies which make my dependencies trees looks very ugly and verbose (and also creates circular trees sometimes).

What I want to do, is walk through the index.js file to the real dependency and add the real dependency only.
This can be done in theory by identifying that the index file is only import and export stuff (without any real logic/change to them).
along with the analyzing of the specific object I imported.

What do you think will be the best way to implement this within your packages?

Thanks a lot,
Gilad.

@mrjoelkemp
Joel Kemp
@mrjoelkemp
@dkebler sorry I missed this message. There is an Atom fork that isn't great but has the right bones. It's atom-dependents
Joel Kemp
@mrjoelkemp
@Asc2011 Coffeescript support isn't planned. If it's for work, we could possibly discuss your company funding the effort for CoffeeScript support. Alternatively, I'm open to PRs that add support for CS (if you're up for contributing).