Satyajit Sahoo
UX Designer
Behance Profile
We're all stories, in the end. Just make it a good one, eh? — The Doctor, Season 5, Episode 13.
I'm not aware of any search path feature in ES6. It just searches the current directory AFAIK. You can do subdirectories and all, but that's it.Satyajit Sahoo
UX Designer
Behance ProfileWe're all stories, in the end. Just make it a good one, eh? — The Doctor, Season 5, Episode 13.
On 21 May 2015 at 18:10, Matěj Cepl <mcepl cepl eu> wrote:On 2015-05-21, 07:50 GMT, Satyajit Sahoo wrote:
> Yeah modules are a must. Right now we need to do the following,
>
> imports.searchPath.unshift(".");
>
> const ModName = imports.filename
This reminds that I still don’t know what is the story of
imports.searchPath (or $LD_LIBRARY_PATH, or $PYTHONPATH, etc.)
in the ES6 universe. Is there such concept in the standard or is
it actually implementation dependent (that would be bad, IMHO)?
> ES6 modules will solve this problem. But then what will happen to the
> current method? It'll suck to use *imports* for the core libraries and
> the *import
I think with
https://bugzilla.mozilla.org/showdependencytree.cgi?id=694100&hide_resolved=1
getting shorter and shorter (and particularly
https://bugzilla.mozilla.org/showdependencytree.cgi?id=568953&hide_resolved=1
is even shorter) there should be some discussion on the future
of GJS in view of the emerging ES6 developments (also classes,
etc.).
Best,
Matěj
--
http://www.ceplovi.cz/matej/, Jabber: mcepl<at>ceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC
understand, v.:
To reach a point, in your investigation of some subject, at
which you cease to examine what is really present, and
operate on the basis of your own internal model instead.
_______________________________________________
_javascript_-list mailing list
_javascript_-list gnome org
https://mail.gnome.org/mailman/listinfo/_javascript_-list