We are trying to build our website with gatsby using gatsby-source-contentful. I've identified a performance problem in the way links are looked up. By using an array as datastructure and doing liniar search, it takes 20-30 mins extra to resolve links.

In my POC I put all the entries in an object with id as key which allowed it to resolve the links immediately.

Looking at the code today it seems like it can support entries and assets with the same id. I don't know if this is a use case that needs to be supported.

Hello
I've tried upgrade contentful-resolve-response from version 1.1.4 to 1.2.2 and I get an error in console: TypeError: Cannot read property 'type' of undefined
I get response from contentful like that:
{ "sys": { "type": "Array" }, "total": 1, "skip": 0, "limit": 100, "items": [ { "fields": { "internalTitle": "Page", "slug": "b", "title": "B", "description": "test", "metaTitle": "B", "metaDescription": "" } } ] }
I think the problem is in lines:
https://github.com/contentful/contentful-resolve-response/blob/master/index.js#L120
and
https://github.com/contentful/contentful-resolve-response/blob/master/index.js#L122
My response responseClone.items doesn't have sys key so it will be undefined.
Can you check it?
In old version, everything works perfectly.

Hey guys, I have a project that copied/modified your code for internal use but couldn't find the license for it.

I see it's MIT, but since MIT usually asks for The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. could you add such a license in this repo ?

Thank you !

Hi there, just thought I should flag something I encountered today. I'm not sure if its a problem with my setup or a general problem.

• Project runs fine in development, with webpack-dev-server
• Rails/Webpacker project being pushed to Heroku
• Heroku runs build/compile, is using Uglify to compile JS
• Uglify can't resolve because of an "unexpected token"

Unexpected token: operator (>) [./node_modules/contentful-resolve-response/index.js:8,0]

Hey there.

We're using webpack as our module bundler, and are pulling in your contentful package in through npm.

I just ran a analyzation of the size of my final JS bundle, and I noticed contentful (and it's dependencies) were the cause of 17.2% of my bundle (616.87 kB) unminified.

After looking into it a bit deeper, contentful-resolve-response is using lodash-contrib, which is probably unnecessary, given the fact that you guys are only using 5 of lodash-contrib's functions.

I'm wondering if you'd be willing to slim down the dependencies here for the sake of bundle sizes everywhere.

Thanks!
-Adam

Despite going through the trouble of making a copy:

It seems that resolveResponse() is mutating its input.

See associated PR for a failing test.

I am getting that error when trying to resolve my json response

Hello - the 1.8.0 release uses the regex /.*:spaces\/(?<spaceId>[^/]+)(?:\/environments\/(?<environmentId>[^/]+))?\/entries\/(?<entityId>[^/]+)$/ which has named capture groups. These are only compatible with browsers that support ES2018 and up. Was wondering if the browser support change was intentional? If not would it be possible to remove the group names since they aren't being used currently? The matching code is just using string.match. Thanks!