atom-build
atom-build copied to clipboard
noseglid
:hammer: Build your project directly from the Atom editor
[Enter steps to reproduce:] 1. ... 2. ... **Atom**: 1.25.0 x64 **Electron**: 1.7.11 **OS**: Mac OS X 10.13.3 **Thrown From**: [build](https://github.com/noseglid/atom-build) package 0.70.0 ### Stack Trace Uncaught RangeError: Invalid string...
[Enter steps to reproduce:] 1. I have 2. no idea 3. sorry ... It seems to happen when also using the platform-io-terminal, I wonder why. Also my Firefox hangs when...
When I add a new target to my .atom-build.json and then do "Packages -> Build -> refresh targets" the new target does not appear in the list of available targets....
With atom-build-waf and some wscript_build builds in sub folders, it failed to open the file. Instead there was a warning, the file does not exist. There is a similar problem...
Fixes noseglid#527 by not using require() to load `.atom-build.*` Coffeescript noseglid#513 was easy to add after that. Did I miss any tests I should've added?
I'm definitely sure this would help me, but I'm not sure what would be the effect on other builds ... so I'm asking here (I can try to implement it...
Build errors don't show up in the atom-ide-ui/nuclide diagnostics ui because atom-ide-ui-diagnostics only consumes linter-indie 2.0 and we provide 1.0 (their diagnostics replaces the linter package) [ide-diagnostics package.json](https://github.com/facebook-atom/atom-ide-ui/blob/c98592b9e2485e4e77a6bfcde2a88477b84bb57e/modules/atom-ide-ui/pkg/atom-ide-diagnostics/package.json#L43) vs [atom-build...
In my case, I had a custom error parser that would produce something that the linter would not like. This would cause an exception (duly reported), but then the busy...
Hi, I open this issue, related to https://github.com/noseglid/atom-build/issues/419. It seems that a command is being registered multiple N times (N is the Opened Project Folders). This is not a desired...
