ng2-semantic-ui: Popper.js error
Bug description:
Getting this error when i want to serve my app with ng2-semantic-ui included:
node_modules/@types/popper.js/index.d.ts (104,3): Cannot redeclare exported variable 'default'.
node_modules/popper.js/index.d.ts (106,24): Cannot redeclare exported variable 'default'
It seems to be related to the recent popper.js update 1.11.0, specifically the addition of types to their package with the pull #351. Manually downgrading popper.js to the older 1.10 branch temporarily helps to avoid the error.
Version of Angular, ng2-semantic-ui, and Semantic UI:
- Angular: 4.3.1
- ng2-semantic-ui: 0.9.3
- Semantic UI: 2.2.11
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 15 (8 by maintainers)
Commits related to this issue
- hotfix(popup): Locked popper.js dependencies until type defs are fixed Closes #195 — committed to edcarroll/ng2-semantic-ui by edcarroll 7 years ago
- chore(popup): Relaxed popper.js dependency Follows up on #195 — committed to edcarroll/ng2-semantic-ui by edcarroll 7 years ago
- chore(popup): Relaxed popper.js dependency (#228) Follows up on #195 — committed to edcarroll/ng2-semantic-ui by edcarroll 7 years ago
- fix: Fixed AOT on SystemJS builder (#240) * fix: Fixed AOT on SystemJS builder Closes #209 * fix: Added custom FocusEvent interface (#231) * fix: Added custom FocusEvent interface Closes ... — committed to edcarroll/ng2-semantic-ui by edcarroll 7 years ago
- hotfix(popup): Locked popper.js dependencies until type defs are fixed Closes #195 — committed to gotenxds/ng2-semantic-ui by edcarroll 7 years ago
- chore(popup): Relaxed popper.js dependency (#228) Follows up on #195 — committed to gotenxds/ng2-semantic-ui by edcarroll 7 years ago
- fix: Fixed AOT on SystemJS builder (#240) * fix: Fixed AOT on SystemJS builder Closes #209 * fix: Added custom FocusEvent interface (#231) * fix: Added custom FocusEvent interface Closes ... — committed to gotenxds/ng2-semantic-ui by edcarroll 7 years ago
Ahh ok I see whats happened. I’ll now that Popper.js is including their own types I no longer need to depend on
@types/popper.js. FYI the reason it’s a dependency is because I re-export a couple of definitions from the lib hence the error. Will get a fix out in the next release.Great, thanks for the quick fix!
0.9.4is now live which locks down the Popper dependencies for now. @mvcoding this will sort out your build.Workaround for now is manually installing
popper.js@1.10.8