-
Notifications
You must be signed in to change notification settings - Fork 11
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.
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
Updates for Nodebb V2 #17
base: main
Are you sure you want to change the base?
Conversation
Ishankhan21
commented
Aug 17, 2022
•
edited
Loading
edited
- Updated how modules are configured for Nodebb V2 based on https://nodebb.org/blog/migration-guide-for-v2/
- Updated version for "async" package because it was giving some issue.
- Fixes Issue Plugin assets aren't building #15
Hey @mooreds, Please review. |
Thanks for the reminder. I'm going to try to review this week. I need to test against both nodebb 2 and nodebb 1.8 before accepting. |
I haven't forgotten about this, but sorry, have been slammed and unable to test. |
@mooreds I manually imported the changes here to my NodeBB installation and they worked if this helps |
Taking a look at this now, sorry for the delay. |
"static/lib/admin.js" | ||
] | ||
"nbbpm": { | ||
"compatibility": "^2.0.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't this mean that it is only compatible with 2.0.0 and above? I tested and it seems to work with 1.18 too.
Heya, I'm having trouble building this for my 1.18 installation. I'd love to see if we can support both 2.x and 1.18. When I check out your branch
I'm using 3.9.10 of tsc:
Is this because nodebb 1.18 doesn't support that version of typescript or for some other reason? |
Any update on this? Can we like have a different versions for nodebb 1.18 and 2.x. |
@mooreds Do you think we can perhaps move on from v1 series of NodeBB with this? 3.1.4 was released last month and I don't think v1 series are supported anymore. |
I just tested this on 1.18 and it works as well. Regarding
After I did
I'm going to attempt to install this in 3.1.4 and see what happens. |
@mooreds the compatibility string is just a hint. If the range specified doesn't encompass v1.18 then it will not show up in the plugin list in the ACP but is of course still installable via command line. |