Skip to content

feat: add UMD build to npm package#357

Merged
ctavan merged 1 commit intonextfrom
add-umd-build
Jan 27, 2020
Merged

feat: add UMD build to npm package#357
ctavan merged 1 commit intonextfrom
add-umd-build

Conversation

@ctavan
Copy link
Copy Markdown
Member

@ctavan ctavan commented Jan 27, 2020

A request for this has popped up a number of times in the issues.

I'm still not sure whether I want to add this. It adds another 28kb to the npm package and I'm not sure whether it's worth supporting such a legacy use case.

Plus there are options like https://bundle.run/uuid@latest?name=uuid

What do you think @broofa ?

@ctavan ctavan requested a review from broofa January 27, 2020 09:58
@broofa
Copy link
Copy Markdown
Member

broofa commented Jan 27, 2020

No strong opinions on this. As long as it doesn't add to the maintenance headache I don't care much one way or the other.

@ctavan ctavan force-pushed the remove-insecure-rng branch from 32e4e86 to 3a5842b Compare January 27, 2020 21:08
@ctavan ctavan changed the base branch from remove-insecure-rng to next January 27, 2020 21:20
@ctavan
Copy link
Copy Markdown
Member Author

ctavan commented Jan 27, 2020

Thought about it again and I think it's an acceptable overhead for a feature that has been requested at least three times last year:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants