[blocking release] es2017 migration breaks custom widget libraries written in es5
See original GitHub issueNow that we target es2017 in core packages, custom widget libraries that subclass WidgetModel
with the es5 syntax don’t work anymore.
The issue is that static properties from the es6 bases are not visible to the derived classes.
Two approach are possible:
- move back to building to es5 in widgetsnbextension
- override
Backbone.Model.extend
in the baseWidgetModel
to properly polyfill the es6extends
including the behavior with respect to static properties.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Migrating custom widget libraries - ipywidgets - Read the Docs
To find the correct version number, go to the releases page on Github and cycle through the tags until you see the latest...
Read more >operation-eyes-widget - npm
To update an existing project to a new version of react-scripts , open the changelog, find the version you're currently on (check package.json...
Read more >What's New - deck.gl
What's New. This page contains highlights of each deck.gl release. Also check our vis.gl blog for news about new releases and features in...
Read more >The React Handbook – Learn React for Beginners
React is a JavaScript library that aims to simplify development of visual interfaces ... by dividing the UI into a collection of components....
Read more >Read PDF Exploring Es6 Epub
Why reinvent the wheel every time you run into a problem with Ja-. vaScript? This cookbook is chock-full of code recipes that address....
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
+1 for the base and controls package. I think it’s probably not necessary to move the jlab manager back to es5.
I am working on a PR reverting the move to es2017.