Dimitris Michalakos

note: the issue linked in the PR description points to the contribution guidelines instead of an actual issue. Is this by mistake?

@jmorrell here's a workaround. It ain't perfect but works... 1. Make sure to add `package.json` under _server_ and _frontend-app_. List dependencies (as you normally do) and specify a _start_ script...

OK, I just realized you are working for Heroku, so this is probably not a real question, but rather a feature request. Sorry for the misunderstanding. In any case, I...

@Arrow7000 yeap, works like a charm. The only problem is caching - see issue #387 even though it's somewhat unrelated to the application structure. See, I am using local files...

@Jan0707 have you tried running gulp on `postinstall` from within the internal package.json file, i.e. `app/Resources/package.json` in your case? Another idea might be to install gulp with root package.json and...

FYI search response contains a `nextPageUrl` property, specifically `response.payload.searchResponse.doc[0].containerMetadata.nextPageUrl`. Using that URL one can iterate over the result pages.

Iterator is an excellent idea! As for exposing new search functionality under a different method name, I believe this is a matter of preference. The way things are going with...