Skip to content

support bower package management #4018

@david-gang

Description

@david-gang

This feature request may be connected to #3257 .

One of the main workflows today, for maintaining dependencies to 3rd parties is through bower.

The bower.json contains all dependencies. Then the bower command line is used to download all modules transitively. Afterwards we use modules like main-bower-files to create a list of files which have to be fetched into the application.

The gulp snippet looks like this

gulp.src(bower_files)
        .pipe(js_filter)
        .pipe(sourcemaps.init())
        .pipe(concat('vendor.js'))
        .pipe(sourcemaps.write('.'))
        .pipe(gulp.dest('lib'));

Afterwards the vendor.js is included into the index.html

The situation now with angular 2 is that it can be just downloaded through npm. Also the bower.json file is missing the main property.

Would it be possible to maintain the bower workflow?
This would mean that packages should be uploaded to bower and the bower.json should be filled out properly.

If not which workflow do you envision ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions