Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Log browserified vendor bundles, and their named exports #1080

Closed
Silic0nS0ldier opened this issue Apr 20, 2020 · 1 comment
Closed

Log browserified vendor bundles, and their named exports #1080

Silic0nS0ldier opened this issue Apr 20, 2020 · 1 comment
Labels
assets Related to the assets feature developer experience The one building with UF

Comments

@Silic0nS0ldier
Copy link
Member

Silic0nS0ldier commented Apr 20, 2020 •
edited
Loading

We run browserify against packages installed with npm to permit consumption without requiring a common-js aware environment, however while this feature exists the impact it has practically invisible to developers. It would be nice if successfully browserified packages were logged during assets installation, including the name of the resulting bundles.

Dependency task: userfrosting/browserify-dependencies#11
@Silic0nS0ldier Silic0nS0ldier added assets Related to the assets feature developer experience The one building with UF labels Apr 20, 2020
@Silic0nS0ldier Silic0nS0ldier mentioned this issue Apr 20, 2020
Open
@lcharette
Copy link
Member

Not relevant in UF5 anymore

@lcharette lcharette closed this as not planned Won't fix, can't repro, duplicate, stale Nov 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
assets Related to the assets feature developer experience The one building with UF
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lcharette @Silic0nS0ldier