Project Status: Maintenance Reboot · Issue #5027 · mochajs/mocha
👋 Hi all! @Uzlopak, @voxpelli, and I are happy to announce that we've picked up maintenance of the Mocha organization and packages. That primarily includes the mocha test framework. Shoutout and thanks to @boneskull for inviting us on and helping set up many of the documentation and processes still in use today, as well as the other recent Mocha core team members: @giltayar, @juergba, @Munter, an
Future of Angular E2E & Plans for Protractor · Issue #5502 · angular/protractor
TLDR The Angular team plans to end development of Protractor at the end of 2022 (in conjunction with Angular v15). Why? Protractor was created in 2013 when WebDriver APIs were not yet a standard and end-to-end (e2e) tests were hard to write due to lack of support for async / await. To solve this problem, Protractor wraps selenium-webdriver and abstracted asynchronous operations from developers wit
webpack 5 release plan · Issue #11406 · webpack/webpack
TL;DR: release planned for 2020-10-10 After nearly 1 year of beta testing and about 2 years of development we feel that it's time to release webpack 5 soon. As promised we do announce the release at least one month earlier to allow the ecosystem to catch up. To support that we will release have released a Release Candidate (RC) soon-ish in about 1-2 weeks. Once the RC has been released we try to a
Request’s Past, Present and Future · Issue #3142 · request/request
Before I go into the details and reasoning I’ll get straight to the point. The most valuable thing request can do for the JavaScript ecosystem is to go into maintenance mode and stop considering new features or major releases. Apologies in advance to the other committers on request that have been doing their best to improve it, but it’s for the best. 2009 The first version of request was one of th
Yarn's Future - v2 and beyond · Issue #6953 · yarnpkg/yarn
Hi everyone, When the Yarn project started back in 2016, our landscape was very different from what it is now. Package locking was far from being a first class citizen in the Javascript ecosystem, and the time needed to run an install was ... well, it was what it was. Yarn's release shook the status quo and started a movement that ended up being beneficial to everyone, other package managers inclu
Renaming jade -> pug · Issue #2184 · pugjs/pug
Unfortunately, these people have a trademark for the word "jade" referring to software, so we've been forced to change our name. Fortunately, @davidglivar has kindly donated the name "pug" to us. I've claimed pug and pugjs everywhere I could think of so hopefully we shouldn't have any problems getting the name. Action items create a new logo (@GarthDB) design new branding for the website (@GarthDB
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Discontinued · Issue #533 · patriksimek/vm2
Security issue: compromised npm packages of ua-parser-js (0.7.29, 0.8.0, 1.0.0) - Questions about deprecated npm package ua-parser-js · Issue #536 · faisalman/ua-parser-js
The future of the hapi project · Issue #4113 · hapijs/hapi
Core: Migrate from AMD to ES modules 🎉 by mgol · Pull Request #4541 · jquery/jquery