-
Notifications
You must be signed in to change notification settings - Fork 1
FAQ
First, none of the others really worked perfectly and exactly the way I wanted them to, and most were lacking guides or documentation. This is definitely something I could deal with though, which leads me to my second, and main reason for making this bundler.
I was just kind of bored and wanted something useful to make ¯\_(ツ)_/¯. I was working on some kind of Webpack configuration for my own plugin development, so I decided to put the work into making it a hopefully easy to use public package. Even if BundleBD isn't the most feature-rich or well optimized Discord plugin bundler on the market, the experience from making a real package (for the first time for me) and utilizing some of the skills I've learned in the past was definitely worth all the effort. And maybe over time it will be able to grow into something better.
Due to how VS Code and Typescript look for type declarations by default, BundleBD's types may not be automatically detected and used for autocomplete. There are a few solutions to this though.
This one is pretty self explanatory. Adding a reference directive to the top of your file will allow Typescript to detect the bundler's types, like so:
/// <reference types="bundlebd" />
export default class Plugin {
start() {
console.log("No more type issues!");
}
stop() {}
}
Using a TSConfig file requires a little extra work, but should automatically detect the bundler's types in every file. Simply make a tsconfig.json
file in your root folder with the following contents:
// tsconfig.json
{
"compilerOptions": {
"types": ["node", "bundlebd"]
}
}
Or, if you're already using a TSConfig file, you can add the types property to it.
For more information on recommended Typescript configuration, see here.
To also detect types in every file, you can create a type declaration file in your project's root with a reference to BundleBD's types. For example:
// global.d.ts
/// <reference types="bundlebd" />
Just make an issue on Github, and I'll be sure to take a look at it and be happy to solve any problems or consider any requests. Make sure your issue thoroughly and clearly describes the bug or feature, and include any other info like examples, images, etc. that might be helpful.