Skip to content

graybeards/bazel

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 

Repository files navigation

Bazel and Bagels

Documenting our journey to using Bazel for our large enterprise Angular/AngularJS application

Where did we start

Goals

  1. Build Login SPA with bazel (requires other 2nd party libraries)
  2. Horse race: Repeatedly build the Login SPA on Jenkins - webpack vs. bazel

TODOs

  • Make a module in espresso/core/components
    • Is there a bug with sass_binary or should we write our own to make files relative. Or option to ngc to say where root of assets are located.
  • Look at source to sass_binary
    • See if we can make the name one thing and output file named something else
  • Instructions on how to add new components
  • Tool to compare (SHA hash) of bagel output vs. webpack
  • Run a dev server
  • Run tests

Nuggets of wisdom

  • Use module_name within ng_module to expose @something/foo module names.

Troubleshooting

References

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors