Nwb: maintenance of NWB library

Created on 11 Jul 2019 · 10Comments · Source: insin/nwb

This issue is a:

Other

Hello!
NWB is such an important library those days where the devop changes frequently and become a complicated yet essential part of the development. I loved that you covered many technology stacks (web, preact, react....) and that you abstract the implementation details yet support the common formats (es modules, umd, lib).

I wanted to ask about the maintenance status of this library as it is been a while since you released new version or pushed new commits, there are deprecation and security warnings on libraries that are used by nwb and issues are not getting attentions.

This is not a criticism, I know how hard it is to try and be on top of all those issues/updates etc. But I would appreciate your answer about the near future planned effort on this library. When are you planning to fix all those deprecations / security issues and release new version?

Thanks!
Eran.

Source

esakal

👍21

Most helpful comment

Hi @esakal, I haven't been using React at work for a couple of years now, which was one of the main things which allowed me to keep nwb updated (as I had to keep it working, and any improvements were benefits to my work), and have had limited time for working on my own projects and open source stuff in general over the last year.

I've had a bit of time this week and I'm surprised at how relatively static things have stayed over the last year and a half - Webpack 4 is still the stable version, as is Babel 7, which I'd already completed 95% of the work to migrate to. There's now also an official solution for React hot reloading, which originally needed a really hacky approach for Babel 7 which stopped me from being happy with merging that branch.

Dependencies are now up to date in master and the Babel 7 branch has been merged, so there'll be a new release soon.

insin on 7 Mar 2020

🎉5

All 10 comments

I agree with this. I would love to help maintain NWB, especially in rolling out features and improvements relevant to the current state of the JS ecosystem. Also, to get rid of these humongous list of warnings:

samrith-s on 28 Jul 2019

👍3

@insin
I'd like some info on the maintenance status of this repository as well. We are about to start developing a relatively large component library using NWB, and generally the initial setup with NWB was a pretty much perfect experience.

The lack of recent activity/updates is the only thing that concerns me. I wouldn't mind helping out with maintenance but considering there haven't been any merged pull requests since 2018 I'd rather not invest any time before understanding if this project is still going anywhere.

bdaenen on 28 Aug 2019

👍3

@insin seems like he hasn't been on github for a couple weeks. Maybe he'll show up soon? I think if we don't get a response within another month it is time to either fork and release a new version of nwb (with a new name under npm --> nwb2) maintained by different people or .. abandon ship for another similar dev tool.

I've loved using nwb for the past couple years and found it has greatly eased development, but if it isn't getting maintained then something will have to be done.

tnrich on 25 Sep 2019

👍1

Speaking of abandoned, does anyone know how to fix the issue where import autocompletes the /es/ path and not the root export? I opened an issue in May and it's October. I feel like maybe it's a simple configuration change but I can't figure it out.

https://github.com/insin/nwb/issues/530