If multiple JavaScript libraries built by lasso are included on the same page, their "loader metadata" can have conflicts. Loader metadata is global so if two of the JavaScript libraries happen to use the same async package name, then the last loaded package definition will clobber the previous package definition.
If multiple JavaScript libraries built by lasso are included on the same page, their "loader metadata" can have conflicts. Loader metadata is global so if two of the JavaScript libraries happen to use the same async package name, then the last loaded package definition will clobber the previous package definition.
I have a fix ready.