Adler Faulkner

For anyone with this problem, you can trick typescript by casting the api method to `jest.Mock` like this: ``` (chrome.tabs.get as jest.Mock).mockImplementation( ... ) ```

+1 for this feature

Reference to relevant part of the JSON-LD spec [https://www.w3.org/TR/json-ld11/#json-literals](https://www.w3.org/TR/json-ld11/#json-literals) > At times, it is useful to include JSON within JSON-LD that is not interpreted as JSON-LD. Generally, a JSON-LD processor...

Ah, I am seeing from this test [https://w3c.github.io/json-ld-api/tests/compact-manifest#tjs07](https://w3c.github.io/json-ld-api/tests/compact-manifest#tjs07) that you have to add `"@container": "@set"` to the context. That seems like a requirement that is not stated in the spec,...

Thanks @gkellogg and @davidlehn. I look forward to seeing those tests and their reception in the WG. It sounds to me like `@set` in the context should always be evaluated...

+1

I'm not sure what you want in `componentsjs-error-state.json`, all I see there are long lists of componentTypes, componentModules, importPaths, nodeModulePaths, and contexts. Here's the full error output: ``` 2022-04-14T06:29:54.017Z [Components.js]...

When I put `console.debug` for the error on line 79 of `ParameterPropertyHandlerRange.js` (the js version in my node_modules folder), I get: ``` SyntaxError: Unexpected token @ in JSON at position...