You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did litle digging and found out that back in the days angular cli was shimming node specific tooling angular/angular-cli@bd4d3c5
if i recreate node shimming with stub impl reding ttls works just fine. that means that library imports node specific things like process or global without using them.
My suggestion is to remove references to node tooling, especially global and process in modules i which they are not used directly (content ttl read is one of examples)
Antoniossss
changed the title
How to use graphy with angular??
Remove references or imports to node specific objects like process or global
Oct 1, 2020
process is used in @graphy/core.iso.stream (a dependency of ttl.read) as a polyfill for browsers and old versions of node https://github.com/blake-regalia/graphy.js/blob/master/src/core/iso/stream.js.jmacs#L194 Next major release drops support for node.js < v12, and readable-stream has standardized .destroy in standalone package away from node core with a browser variant. So next release should avoid this particular issue. At least for v4 in the meantime there is a workaround. Thanks for posting.
Since it supposed to work with webpack I should be able to use it out of the box. However
npm install --save @graphy/content.ttl.read
and than in method
fails with
Also I had to add
<script> global=globalThis </script>to the index.html as it was failing with
global
is undefined errorThe text was updated successfully, but these errors were encountered: