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
Starting from v1.12.0, Popper.js is installable by Bower directly without use of unpkg.com CDN.
Now the bad part:
I can't find a way to make Bower work together with Lerna.
Since Bower takes the whole repository as source of the package, it will clone inside your bower_components folder the whole repository containing the packages/ folder.
There's not any bower.json at the root level, because the bower.json are supposed to be stored in each package folder.
For the moment, we copy the dist/ folder and the bower.json of packages/popper.js from its folder to the root directory, but this limits our ability to publish to Bower more than a single package.
If no ways to manage multiple packages is found, I'll deprecate Bower support starting from Popper.js@2
The text was updated successfully, but these errors were encountered:
First, the "good" news:
Starting from v1.12.0, Popper.js is installable by Bower directly without use of unpkg.com CDN.
Now the bad part:
I can't find a way to make Bower work together with Lerna.
Since Bower takes the whole repository as source of the package, it will clone inside your
bower_components
folder the whole repository containing thepackages/
folder.There's not any
bower.json
at the root level, because thebower.json
are supposed to be stored in each package folder.For the moment, we copy the
dist/
folder and thebower.json
ofpackages/popper.js
from its folder to the root directory, but this limits our ability to publish to Bower more than a single package.If no ways to manage multiple packages is found, I'll deprecate Bower support starting from Popper.js@2
The text was updated successfully, but these errors were encountered: