| { | |
| "version": "2.0.0", | |
| "tasks": [ | |
| { | |
| "label": "Compile C file with cc.", | |
| "type": "shell", | |
| "command": "cc ${relativeFile}", | |
| "windows": { | |
| "command": "gcc ${relativeFile}" | |
| }, |
npm init in the folder to setup in.
type to package.json and set it to commonjs. We will be compiling TypeScript to CommonJS for execution, so when node executes the compiled files it should do it as CJS.discord.js: npm i discord.js @discordjs/rest discord-api-types @discordjs/builders
discord.js is the main package for connecting to Discord with node.js@discordjs/rest to authorise a connection to the Discord API
Recently, I began a new endeavour on a new project that would hopefully expand upon some of my old skills and start to expose new technologies I hadn't yet had the chance to work in. I chose to make a 'UI Kit', or in this case a React Component Library. What I hadn't expected was how difficult it would be to get a project like this off the ground.
My first goal was to create a package that I could include in other projects as a node module that would have many different preset React components included to speed up development time / mimic professional workflows. Because I had never done anything like this, I would need to wrap my head somewhat around many new technologies, including Bundlers, Rollup, Storybook, and eventually TypeScript as I thought it would be a good chance to learn how.
Ultimately, the setup phase involved the following: