Skip to content

Expose Tether's default export, not the module namespace #234

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
boo-code wants to merge 1 commit into
base: develop
Choose a base branch
from
Draft

Expose Tether's default export, not the module namespace #234

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion _dev/js/theme.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,11 @@
* @license https://opensource.org/licenses/AFL-3.0 Academic Free License 3.0 (AFL-3.0)
*/
/* eslint-disable */
import 'expose-loader?exposes=Tether!tether';
// tether 2.x ships an ES module whose default export is the class, and webpack resolves it through
// the package's `module` field, so exposing the import itself puts the namespace object on
// window.Tether - `new Tether(...)` then throws "Tether is not a constructor" and Bootstrap's
// tooltips and popovers stay broken. `|default` exposes the export instead of the namespace.
import 'expose-loader?exposes=Tether|default!tether';
import 'bootstrap/dist/js/bootstrap.min';
import 'flexibility';
import 'bootstrap-touchspin';
Expand Down
Loading