NewPluginsManager

[pliant latch]

Utility that notifies you when new plugins are added to Vencord
Useful for people who install 3rd party plugins, and developers frequently writing their own plugins.

Repo: https://github.com/Sqaaakoi/vc-newPluginsManager
Clone: git clone https://github.com/Sqaaakoi/vc-newPluginsManager

[spring slate]

funnily enough when you install 3rd part plugins and filter by new it shows the 3rd party plugin as new

[pliant latch]

that is vencord's internal new plugins system based on date

I plan to add new settings popup

[tight rose]

adding a tab in settings to open available plugins on demand would be dope as well

[tame parcel]

Love

You

[pliant latch]

Update
It's been too long, but I've finally added detection for new settings to the plugin

[pliant latch]

Update
Redesigned this tooltip. Temporary dismiss button will be fixed soon

[sharp moth]

YOO

[pliant latch]

Update
After a month and a half, I've finally decided to fix the issues in this plugin

Added a "Don't show this again" checkbox (as the plugin is intentionally enabled by default)

Fixed the "Dismiss for this session" close button tooltip and placement

The plugin will no longer detect saved settings and will now detect registered settings. This should result in accurate detection of when new settings are added and stops detection of removed settings that have been synced from other clients.

[stuck tusk]

will this update 3rd party plugins

[pliant latch]

It does not, this just tells you when new plugins have been added or settings have been added for those plugins.
This feature might be suited for an addition to #1302000818131828810 though, so I'd recommend asking there

[pliant latch]

Update
Fixed the broken Checkbox find causing a crash on canary clients
Added basic error handling (ErrorBoundary around the modal)

[craggy hawk]

I deleted the old version of your plugin and installed new version and it stopped my crashing

[prisma arrow]

My Vencord stopped working again

I updated spotifylyrics and colorways

and suddenly all the vencord tabs in settings say "failed to render blah blah blah, use the installer to fix"

I did run pnpn inject

and tried repairing, didn't work

I then tried to reinstall

Also didn't work

[craggy hawk]

if you remove all plugins does it work

[prisma arrow]

well apparently I can't get support and people are discouraged to reply

sorry

oh actually

apparently I can do it here

if it's related to the plugin

[craggy hawk]

even if i can do it here i get discouraged by saying something the venbot is allowed to say but i cant say

[prisma arrow]

welp

[copper path]

Hi! Since the pinned post tells me to not ask in the support chats, I ask here instead: I've gone through the guides, cloned the plugin repos, everything builds, Vesktop still runs after pointing it to the folder, … but the plugins don't show up in the list. I have folders for each plugin in src/userplugins and those folders contain index.tsx and other files. Anything I'm missing or are custom plugins broken in the current version?

[copper path]

Somehow it works now. I did nothing other than adding even more plugins, rebuilding again and restarting Vesktop. 🤷

[split cave]

was going through the same problem, the solution was just to rebuild and inject for user plugins to appear

the more you know, ig.

[unkempt oasis]

    src/plugins/vc-newPluginsManager/NewPluginsModal.tsx:11:27:
X       11 │ import { PluginCard } from ["@components/PluginSettings";
         ╵                            ERROR~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  You can mark the path "@components/PluginSettings" as external to exclude it from the bundle,
  which will remove this error and leave the unresolved path in the bundle.

] Could not resolve "@components/PluginSettings"

    src/plugins/vc-newPluginsManager/NewPluginsModal.tsx:11:27:
      11 │ import { PluginCard } from "@components/PluginSettings";
         ╵                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  You can mark the path "@components/PluginSettings" as external to exclude it from the bundle,
  which will remove this error and leave the unresolved path in the bundle.

1 error
1 error
Build failed with 1 error:
src/plugins/vc-newPluginsManager/NewPluginsModal.tsx:11:27: ERROR: Could not resolve "@components/PluginSettings"
 ELIFECYCLE  Command failed with exit code 1```

[livid forge]

i'm having the same error

[lyric ermine]

Go to .\src\userplugins\vc-newPluginsManager\NewPluginsModal.tsx and change line 11 from:

import { PluginCard } from "@components/PluginSettings";

to:

import { PluginCard } from "@components/settings/tabs/plugins/PluginCard";

[lyric ermine]

@pliant latch hey there, I opened a PR to fix the plugin. It was a while ago, but I didn't want to ping you because of your nickname, hehe.
https://github.com/Sqaaakoi/vc-newPluginsManager/pull/1

[inner aurora]

Would be handy yes

[lucid rapids]

ping me when its works

[inner aurora]

This is a fix you can do by yourself but you gotta do it every time you install it back (git clone …) #1261020624130932836 message

(It’s a message button, click it)

[lucid rapids]

mh, I Will try it tomorrow

thanks btw

[winged hill]

thanks for the fix

[inner aurora]

Since the owner didn't merge the pull request yet, he's how to fix it automatically using the git clone method
-# using Benjas333's fix.

git clone https://github.com/Sqaaakoi/vc-newPluginsManager
cd vc-newPluginsManager
git fetch origin 99746f0b7e9d007e36df2a0b2fee8c2b77300655
git cherry-pick 99746f0b7e9d007e36df2a0b2fee8c2b77300655
cd ..

for a manual fix,
./NewPluginsModal.tsx

line 11: import { PluginCard } from "@components/settings/tabs/plugins/PluginCard"

(changes)

- Line 11: import { PluginCard } from "@components/PluginSettings";
+ Line 11: import { PluginCard } from "@components/settings/tabs/plugins/PluginCard"

[inner aurora]

-# useful for automatic complete rebuild

[formal knoll]

X [ERROR] No matching export in "src/webpack/common/index.ts" for import "Flex"

    src/userplugins/vc-newPluginsManager/NewPluginsModal.tsx:17:17:
      17 │ import { Button, Flex, Forms, React, Text, Tooltip, useMemo } from "@webpack/common";
         │                  ~~~~
         ╵                  Flux

  Did you mean to import "Flux" instead?

    src/webpack/common/stores.ts:24:13:
      24 │ export const Flux: t.Flux = findByPropsLazy("connectStores");
         ╵              ~~~~

uhhh

[inner aurora]

Look the msg above

[formal knoll]

did all of it

[red plover]

did both fixes and it still didn't go through 😭

[inner aurora]

What is the error? Check the pull requests or issues in the githuv

[red plover]

same exact as the person above me

[inner aurora]

Since the owner didn't merge the pull request yet, here's how to fix it automatically using the git clone method
-# using Benjas333's fix.

git clone https://github.com/Sqaaakoi/vc-newPluginsManager
cd vc-newPluginsManager
git fetch origin 90bc79bb125a4b12b1638960f55017265246282a
git cherry-pick 90bc79bb125a4b12b1638960f55017265246282a
cd ..

@red plover@formal knoll

[red plover]

hm I just tried it and it doesn't find %file% at the powershell -Command line

Get-Content : Der Pfad "C:\...\Documents\Vencord\src\userplugins\vc-newPluginsManager\%file%" kann nicht
gefunden werden, da er nicht vorhanden ist. (<- this basically says it can't be found because it doesn't exist)
In Zeile:1 Zeichen:2
+ (Get-Content '%file%') -replace 'Flex','Flux' | Set-Content '%file%'
+  ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\...\...sManager\%file%:String) [Get-Content], ItemNotFoundEx
   ception
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetContentCommand

[inner aurora]

Ran this in cmd? and got ran the previous line in the same windows?

set "file=NewPluginsModal.tsx"
powershell -Command "(Get-Content '%file%') -replace 'Flex','Flux' | Set-Content '%file%'"

Those both, after using CD to get in the plugin's folder

[red plover]

I ran all previous commands and am in the vc-newPluginsManager folder

it accepts the "set" line but throws up the error on the 2nd one

[inner aurora]

Try

powershell -Command "(Get-Content 'NewPluginModal.tsx') -replace 'Flex','Flux' | Set-Content 'NewPluginsModal.tsx'"

[red plover]

that went through

lemme try building

[red plover]

yup that works perfect

I corrected a typo in NewPlugin__s__Modal.tsx

thank you so much 🙏🏻

[south tapir]

Flex and Flux are completely different things wtf 😭

[inner aurora]

Closest define i found back then 😭 and it seems to be working

[lyric ermine]

Btw, my PR has had a commit that uses the right Flex and updates the deprecated components:
https://github.com/Sqaaakoi/vc-newPluginsManager/pull/1/commits/90bc79bb125a4b12b1638960f55017265246282a

As the owner appears to have abandoned the plugin, I would consider make a maintenance fork or something like that (I don't know how the server rules would apply in this kind of scenarios).

[inner aurora]

I mean a fork would be ideal (a rule against would be weird) but it would require smn active to maintain it

[ancient panther]

I got a build error with your PR:

Done in 139ms
X [X [ERROR]ERROR Unexpected "<<"

    src/userplugins/vc-newPluginsManager/NewPluginsModal.tsx:11:0:
      11 │ <<<<<<< HEAD
         ╵ ~~

] Unexpected "<<"

    src/userplugins/vc-newPluginsManager/NewPluginsModal.tsx:11:0:
      11 │ <<<<<<< HEAD
         ╵ ~~


  dist\vencordDesktopMain.js             36.5kb
  
  dist\dist\vencordDesktopMain.js.LEGAL.txt    patcher.js964b
  40.5kbdist\
  dist\vencordDesktopMain.js.map        patcher.js.LEGAL.txt218.3kb    964b 
  dist\patcher.js.map        

234.9kbDone in 869ms


Done in 869ms
1 error
1 error
Build failed with 1 error:
src/userplugins/vc-newPluginsManager/NewPluginsModal.tsx:11:0: ERROR: Unexpected "<<"
 ELIFECYCLE  Command failed with exit code 1.

[inner aurora]

This shouldn’t be valid chars in a .tsx
Check its content

[ancient panther]

says it's on line 11

sending the first 30 lines from my .tsx

/*
 * Vencord, a Discord client mod
 * Copyright (c) 2024 Vendicated and contributors
 * SPDX-License-Identifier: GPL-3.0-or-later
 */

import "./NewPluginsModal.css";

import { Settings, useSettings } from "@api/Settings";
import { classNameFactory } from "@api/Styles";
<<<<<<< HEAD
import { PluginCard } from "@components/PluginSettings";
=======
import { BaseText } from "@components/BaseText";
import { Button } from "@components/Button";
import ErrorBoundary from "@components/ErrorBoundary";
import { Flex } from "@components/Flex";
import { Paragraph } from "@components/Paragraph";
import { PluginCard } from "@components/settings/tabs/plugins/PluginCard";
>>>>>>> 90bc79b (Fixed import)
import { ChangeList } from "@utils/ChangeList";
import { classes, Margins } from "@utils/index";
import { closeModal, ModalCloseButton, ModalContent, ModalFooter, ModalHeader, ModalProps, ModalRoot, ModalSize, openModal } from "@utils/modal";
import { useForceUpdater } from "@utils/react";
import { findComponentByCodeLazy } from "@webpack";
import { React, Tooltip, useMemo } from "@webpack/common";
import { JSX } from "react";

import Plugins from "~plugins";

[inner aurora]

Well remove it, looks like an http request or shit that lost itself

[ancient panther]

weird

well it worked, thanks

[lyric ermine]

it's a merge conflict

probably because of the ScattrdBlade's commit

[ancient panther]

I did that with a fresh clone

[lyric ermine]

conveniently, my proposal for a maintenance fork would avoid merge conflicts 🗿 /hj

[inner aurora]

I wouldn’t find a reason to disallow it but ig we could ask a mod just to be sure