Discuss
  • Current module path

Current module path

# Maël Nison (11 years ago)

Will ES6 have a way to know what is the current module path from inside a module ?

Such a thing could be useful to locate relative resources, just like node's __dirname global.

# Caridy Patino (11 years ago)

you will be able to access name and address, as well as importing relative modules (on demand).

we should have some concrete examples in about a week, in the meantime, here are the "informal" notes from the breakout session about modules (from two days ago): gist.github.com/caridy/eefb9b104874465d4e1c

# Kevin Smith (11 years ago)

we should have some concrete examples in about a week, in the meantime, here are the "informal" notes from the breakout session about modules (from two days ago): gist.github.com/caridy/eefb9b104874465d4e1c

Thank you for providing this link. I see several names that I do not recognize as TC39 members from previous meeting notes. May I ask who is currently working on the module design?

Thanks,

# Kevin Smith (11 years ago)

On a meta level, I'm continually frustrated by the fact that participants in the module design refuse to share their ideas on es-discuss until a TC39 meeting review is posted (which usually coincides with some kind of "resolution"). Community input is a good thing, right?

# Erik Arvidsson (11 years ago)

Agreed. Side discussions are sometimes needed but please make sure we keep track of what was discussed. For the last TC39 I asked everyone that did a breakout session to take notes and share these. Caridy did a really good job sharing these notes.

# Axel Rauschmayer (11 years ago)

Actually, that is something that I do understand. esdiscussions can be unproductive and emotional. Thus: it’s a tricky balance – getting work done vs. keeping everybody informed and getting feedback. I don’t believe in design by democracy.

David Herman has mentioned on Twitter that he’ll write up the rationales for the decisions in a Gist in the coming week. I’m looking forward to reading that.

# Kevin Smith (11 years ago)

Actually, that is something that I do understand. esdiscussions can be unproductive and emotional. Thus: it’s a tricky balance – getting work done vs. keeping everybody informed and getting feedback. I don’t believe in design by democracy.

Nor do I. It seems to me that the design process of Proxies hit that balance very well (but that could just be my perspective).

# Maël Nison (11 years ago)

I haven't seen module.name / module.address in the latest draft, have they been discussed?

# Axel Rauschmayer (11 years ago)

This is the most recent information on module meta-data:

esdiscuss.org/topic/es6