Skip to content

Issues: bevry/boundation

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

7 Open 40 Closed
7 Open 40 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

If the project is npm + browsers + kava, enable browser testing enhancement Improvement or suggestion PR / Bounty only External demand, as such, external funding / effort is required to make this happen
#167 opened Jan 20, 2024 by balupton
order editions based on newest target version first
#164 opened Nov 30, 2023 by balupton
Consider shrinking editions that only add compat to unsupported versions
#155 opened Nov 2, 2023 by balupton
Add arm or apple-silicon architectures when they become available for github actions
#96 opened Dec 9, 2020 by balupton
1
don't use esm or support esm for typescript modules that still use require
#66 opened Jul 22, 2020 by balupton
add git remote origin (set to the specified git url) if it doesn't exist
#21 opened Nov 14, 2018 by balupton
provide a service to auto apply boundation updates
#18 opened Aug 8, 2018 by balupton
1
ProTip! Add no:assignee to see everything that’s not assigned.