Roddy Pratt

It looks like not. I was importing fengari separately (which has no distributed bundles?) rather than using the API calls exposed by fengariweb etc. So probably due to my Typescript...

OK, I have it working now, as long as I always `import {lua} from "fengari-web"` rather than from "fengari"., for example. ( I hadn't previously made the fengari-web typings re-export...

If I explicitly `import * from "fengari"` (which AFAICT has no distributed bundle) then webpack scans the fengari code for "require"d modules and attempts to add them to the bundle....

I'm actually working on this now, I have most of the API functions defined, and a typescript version of lapi.test.js which compiles and runs cleanly.

Not sure if reproducable but I had this today too. Editing an nginx.conf file, if that's any help. **Atom**: 1.18.0 x64 **Electron**: 1.3.15 **OS**: Microsoft Windows 10 Pro **Thrown From**:...

Suffering exactly the same here. I seems to be really struggling with the whole concept of NODE_ENV, though. Setting it to "production" to make Atom work seems to mean that...

> @mischnic I'm honestly not sure, it's really inconsistent. This. It's not always repeatable but I get it once or twice a day. Steps are as above. AFAICT editing any...

I've also seen cases where the linter shows spurious errors when using multiple panes. Demo here (sorry about crap audio) https://screencast-o-matic.com/watch/cb1o2eXRGd Doesn't seem to happen with Atom PHP linter.

@Xapphire13 You're right, of course. I'm new to Atom and hadn't sussed the distinction between the two plugins. I'll move the report and video over. Thanks! (Appears to be a...