about summary refs log tree commit diff
path: root/pkgs/development/web
AgeCommit message (Collapse)AuthorFilesLines
2023-11-15Merge branch 'master' into staging-nextVladimír Čunát1-2/+2
2023-11-14nodejs_21: 21.1.0 -> 21.2.0Mario Rodas1-2/+2
Changelog: https://github.com/nodejs/node/releases/tag/v21.2.0
2023-11-10Merge staging-next into staginggithub-actions[bot]2-4/+4
2023-11-10Merge remote-tracking branch 'origin/master' into HEADAlyssa Ross2-4/+4
Conflicts: pkgs/development/libraries/SDL2/default.nix
2023-11-10Merge pull request #265452 from r-ryantm/auto-update/grailsOTABI Tomoya1-2/+2
grails: 6.0.0 -> 6.1.0
2023-11-10Merge pull request #265572 from r-ryantm/auto-update/publiiOTABI Tomoya1-2/+2
publii: 0.43.0 -> 0.43.1
2023-11-09Merge staging-next into staginggithub-actions[bot]1-5/+5
2023-11-09Merge master into staging-nextgithub-actions[bot]1-5/+5
2023-11-09bun: 1.0.10 -> 1.0.11Corné Dorrestijn1-5/+5
2023-11-09lib.systems: elaborate Rust metadataAlyssa Ross3-9/+6
We need this stuff to be available in lib so make-derivation.nix can access it to construct the Meson cross file. This has a couple of other advantages: - It makes Rust less special. Now figuring out what Rust calls a platform is the same as figuring out what Linux or QEMU call it. - We can unify the schema used to define Rust targets, and the schema used to access those values later. Just like you can set "config" or "system" in a platform definition, and then access those same keys on the elaborated platform, you can now set "rustcTarget" in your crossSystem, and then access "stdenv.hostPlatform.rustcTarget" in your code. "rustcTarget", "rustcTargetSpec", "cargoShortTarget", and "cargoEnvVarTarget" have the "rustc" and "cargo" prefixes because these are not exposed to code by the compiler, and are not standardized. The arch/os/etc. variables are all named to match the forms in the Rust target spec JSON. The new rust.target-family only takes a list, since we don't need to worry about backwards compatibility when that name is used. The old APIs are all still functional with no warning for now, so that it's possible for external code to use a single API on both 23.05 and 23.11. We can introduce the warnings once 23.05 is EOL, and make them hard errors when 23.11 is EOL.
2023-11-09Merge master into staging-nextgithub-actions[bot]1-5/+5
2023-11-09Merge pull request #266007 from cornedor/update-bun-1.0.9Weijia Wang1-5/+5
bun: 1.0.7 -> 1.0.10
2023-11-07Merge master into staging-nextgithub-actions[bot]2-8/+8
2023-11-07deno: 1.37.2 -> 1.38.0winston2-8/+8
2023-11-07bun: 1.0.7 -> 1.0.10Corné Dorrestijn1-5/+5
2023-11-05Merge master into staging-nextgithub-actions[bot]1-6/+5
2023-11-05publii: 0.43.0 -> 0.43.1R. Ryantm1-2/+2
2023-11-04grails: 6.0.0 -> 6.1.0R. Ryantm1-2/+2
2023-11-04flyctl: 0.1.104 -> 0.1.117Stanisław Pitucha1-6/+5
Update tags and build info handling
2023-11-04Merge master into staging-nextgithub-actions[bot]2-2318/+876
2023-11-03pnpm-lock-export: unstable-2023-07-31 -> unstable-2023-07-31R. Ryantm2-2318/+876
2023-11-02Merge master into staging-nextgithub-actions[bot]1-3/+3
2023-11-02minify: 2.20.1 -> 2.20.5R. Ryantm1-3/+3
2023-10-31Merge #263847: nodejs_18: fix build with clang 16Vladimír Čunát2-129/+13
...into staging-next
2023-10-31Merge master into staging-nextgithub-actions[bot]3-20/+20
2023-10-31lucky-cli: 1.0.0 -> 1.1.0Peter Hoeg3-20/+20
2023-10-31Merge master into staging-nextgithub-actions[bot]1-3/+3
2023-10-30minify: 2.20.0 -> 2.20.1Anton Mosich1-3/+3
See https://github.com/tdewolff/minify/releases/tag/v2.20.1
2023-10-29Merge master into staging-nextgithub-actions[bot]1-3/+3
2023-10-29nodejs_18: fix build with clang 16 mk2Randy Eckenrode1-1/+13
Trying to backport the fixes from v8 caused crashes with npm when building other packages, so just build it with clang 15.
2023-10-29Revert "nodejs_18: fix build with clang 16"Randy Eckenrode2-128/+0
This reverts commit 81e4ca55c823f476882750559e6ccbfd0c445980.
2023-10-28minify: 2.19.10 -> 2.20.0Anton Mosich1-3/+3
See https://github.com/tdewolff/minify/releases/tag/v2.20.0
2023-10-26nodejs_18: fix build with clang 16Randy Eckenrode2-0/+128
Backport a patch from v8 that resolves an enum width error when building with clang 16.
2023-10-26Merge branch 'staging' into staging-nextVladimír Čunát3-3/+34
2023-10-25Merge pull request #263323 from r-ryantm/auto-update/denoMario Rodas2-8/+8
deno: 1.37.1 -> 1.37.2
2023-10-25deno: 1.37.1 -> 1.37.2R. Ryantm2-8/+8
2023-10-25nodejs_21: 21.0.0 -> 21.1.0Mario Rodas1-2/+2
Diff: https://github.com/nodejs/node/compare/v21.0.0...v21.1.0 Changelog: https://github.com/nodejs/node/releases/tag/v21.1.0
2023-10-25nodejs_20: 20.8.1 -> 20.9.0Mario Rodas1-2/+2
Diff: https://github.com/nodejs/node/compare/v20.8.1...v20.9.0 Changelog: https://github.com/nodejs/node/releases/tag/v20.9.0
2023-10-22Merge staging-next into staginggithub-actions[bot]1-5/+5
2023-10-22Merge pull request #262575 from cornedor/update-bun-1.0.7OTABI Tomoya1-5/+5
bun: 1.0.6 -> 1.0.7
2023-10-21Merge staging-next into staginggithub-actions[bot]1-3/+3
2023-10-21Merge remote-tracking branch 'origin/master' into staging-nextAlyssa Ross1-3/+3
Conflicts: pkgs/development/python-modules/velbus-aio/default.nix
2023-10-21bun: 1.0.6 -> 1.0.7Corné Dorrestijn1-5/+5
2023-10-21Merge pull request #262360 from antonmosich/minify-updateWeijia Wang1-3/+3
minify: 2.12.9 -> 2.19.10
2023-10-20minify: 2.12.9 -> 2.19.10Anton Mosich1-3/+3
See https://github.com/tdewolff/minify/releases/tag/v2.19.10
2023-10-20Merge staging-next into staginggithub-actions[bot]1-0/+19
2023-10-20Merge master into staging-nextgithub-actions[bot]1-0/+19
2023-10-19nodejs_16: work around building with clang 16Randy Eckenrode1-1/+13
Node v16 can’t build with clang 16 due to `-Wenum-constexpr-conversion` errors. Since the backport patch from v8 does not apply to Node v14, and it is likely this will become a hard error in future versions of clang, use clang 15 when the version in the stdenv is newer. The version of libc++ used with the clang is made to match the one used in the stdenv to avoid possible issues with mixing multiple versions of libc++ in one binary (e.g., icu links against libc++).
2023-10-19nodejs_14: work around building with clang 16Randy Eckenrode1-2/+14
Node v14 can’t build with clang 16 due to `-Wenum-constexpr-conversion` errors. Since the backport patch from v8 does not apply to Node v14, and it is likely this will become a hard error in future versions of clang, use clang 15 when the version in the stdenv is newer. The version of libc++ used with the clang is made to match the one used in the stdenv to avoid possible issues with mixing multiple versions of libc++ in one binary (e.g., icu links against libc++).
2023-10-19nodejs: clang 16 compatibility for x86_64-darwinRandy Eckenrode1-0/+6
Make aligned allocations work on x86_64-darwin by ensuring libc++ uses `posix_memalign` instead of `aligned_alloc`, which was added in 10.15.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-21 02:36:30 +0000