Iyobo Eki

@timcreative please merge

@rockmandash how did you move forward with this?

Personally, I would advise against using this library in any React app. Visually, it looks really good and slick....but It's reliance on dom-attribute-scraping severely breaks some key react precepts and...

@themoonrat thanks for the response. It does raise several other questions however - i.e - I'm confused as to why it keeps track of loader.resources (equivalent type Hashtable) if the...

Can concur that source-maps are not respected in error outputs despite the fact that they look like they are being generated in the file system. E.g in the case of...

Thanks @david0673 . Could you leave some tips on how to use chunking as is suggested here? From what I see in the code, we'd add options to bulk.query(..) i.e:...

@david0673 There is actually something wrong with this branch. This used to work, but now it doesn't. ``` sfconn.bulk.query(soql) .stream() .on('error', function (e) { errHandler(e, this); }) .pipe(process.stdout) .on('end', function...

@david0673 Thanks for being awesome! Now I'm curious if we aren't bubbling up errors as we should if the null options caused the earlier stall. That Null pointer error seemed...

Could this still happen? Bulk insertion is a very important feature for serious apps

@lucasfcosta No. The issue here is that the errors thrown in beforeAll are getting swallowed, **particularly when using an async function**. They come in as hidden unhandled promise exceptions instead....