Difference between revisions of "Bower"

From OpenEMR Project Wiki
(Redirected page to Composer and NPM)
 
(149 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Overview=
#REDIRECT [[Composer and NPM]]
:Added this to attempt to standardize the assets that are used by openemr.
=Plan=
Assets that are collected via bower are stored at interface/static; note this location is flexible since we are not sure where we will be storing these in the future as migrate to MVC architecture.
:*The path is set to a global ($GLOBALS['assets_static_relative']) here in the codebase(so the path will be easy to change in the future) and also would need to be changed in the .bowerrc file):
::*https://github.com/openemr/openemr/commit/b63b0da6a5eae6f8051234bff104a06cb37db167
::*(also see above commit for a example on using the global/path)
:*Incorporating the versions in the paths of the libraries. Using "ignoredDependencies" in .bowerrc file to ignore sub-dependencies which makes things messy(would bring in paths without versions of which would be a redundant library).
=Implementation=
:Current assets are:
:*font-awesome-4-6-3 (commit is pending)
:*literallycanvas-0-4-13 (commit is pending)
::*Placed "react" as "ignoredDependencies" in .bowerrc file.
:*react-15-1-0 (commit is pending)
=Questions=
:'''<span style="color:red;">Development is ongoing for this project</span>''':
:*Ideal directory for this stuff (this is why we have made it flexible so can easily change this in the future)
:*Ideal syntax of the bower openemr package
:*Use this only for front-end libraries (css/js)?
:*Use composer for back-end libraries? If so, use separate directory?
:*Should we be using bower for this or is it better to manually bring in packages in a standard fashion?
=Forum=
:*[https://sourceforge.net/p/openemr/discussion/202506/thread/d4ec2b8b/ assets directory]

Latest revision as of 07:28, 1 September 2018

Redirect to: