'Element' is not exported from '@prismicio/richtext'.
See original GitHub issueFresh install of @prismic/react v2.0.3 throws error:
Attempted import error: 'Element' is not exported from '@prismicio/richtext'.
Reverting to 2.0.2 fixes the issue
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
webstorm: what does "Element is not exported" warning ...
Obviously Webstorm/IntelliJ recognized the properties as something that should not be exported. export class someOne { constructor(param) { this.
Read more >'Element' is not exported · Issue #2563 · ionic-team/stencil
14 or higher then I get this error saying that Element is no longer exported. Steps to reproduce: To reproduce,. import { Element...
Read more >HTML Serializer - Documentation
In Prismic, Rich Text is stored in an array. An HTML Serializer is a function that defines how the elements of that array...
Read more >'Element is not exported' warning on member in es6 ...
I get "Element is not exported" warning on following code. export default class{ constructor() { this.bar = 1; }
Read more >Vue and Prismic rich text: add event listener to a span node ...
Elements; export default function (type, element, content, children) { // I'm not 100% sure if element.className is correct, investigate with your devTools ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the release! This update does indeed fix the issue for me.
This should be resolved by updating to
@prismicio/react
v2.0.6
.Some background on why this error happens is available here: #122
@stefanstaynimble @BillyBlaze @levimykel Could you let me know if this update fixes the issue? Thanks!