const ɁɁɁ = () => { throw new Error('Method not defined'); };
Thomas Grainger
On 26 March 2018 at 06:26, Isiah Meadows wrote:
> Even in TypeScript, `never` (the type of functions that never return -
> throwing ≠ returning) is the subtype of *all* types, even primitives.
> -
>
> Isiah Meadow
`global.rootRequire` is quite bad (like user-added globals in general), I'd
just do that https://gist.github.com/branneman/8048520#gistcomment-2247189,
or use lerna, or use webpack resolvers
2018-03-29 17:37 GMT+02:00 T.J. Crowder :
> On Thu, Mar 29, 2018 at 2:49 PM, Sebastian Malton
> wrote:
>
On Wed, Apr 4, 2018 at 8:11 AM, Thomas Grainger wrote:
>
> const ɁɁɁ = () => { throw new Error('Method not defined'); };
LOL. Awkward to type on most keyboards, though. :-) Suppose one could use
some form of auto-correct in one's IDE...
-- T.J. Crowder
___
We still use ES5 for development, since our server-side platform (GPSEE)
doesn't run on later SpiderMonkey (embedding API made massive changes a
couple of years ago and we haven't had resources to update.massive
changes)
I am working closely with another company right now that uses NodeJS. It
Could
```js
from 'name' import something;
```
be added to ES module grammar?
which would work like the current
```js
import something from 'name';
```
The advantage is to sort more easily import, and have autocompletion of
imported identifiers
___
es-d
Personally I like this syntax better, but feel that changing or adding
import syntax at this point I'd a non-starter... Not sure what others feel
about this one.
On Wed, Apr 4, 2018, 09:23 Cyril Auburtin wrote:
> Could
> ```js
> from 'name' import something;
> ```
>
> be added to ES module gram
6 matches
Mail list logo