mrjacz / hastebin-gen

A npm module for generating hastebin links.

hastebin-gen

A npm module for generating hastebin links. https://www.npmjs.com/package/hastebin-gen

Installation

NPM: npm i hastebin-gen

Yarn: yarn add hastebin-gen

Options

Option	Type	Default Value
url	string	"https://hastebin.com"
extension	string	"js"

Examples

Using .then().catch()

const hastebin = require("hastebin-gen");

// You can change the extension by setting the extension option
hastebin("code", { extension: "txt" }).then(haste => {
    // Logs the created hastebin url to the console
    console.log(haste); // https://hastebin.com/someid.txt
}).catch(error => {
    // Handle error
    console.error(error);
});

Using async/await

This is assuming that you are in a asynchronous scope

Understanding Async/Await

const hastebin = require("hastebin-gen");

// You can change the extension by setting the extension option
const haste = await hastebin("code", { extension: "txt" });

// Logs the created hastebin url to the console
console.log(haste); // https://hastebin.com/someid.txt

Example with a custom haste-server instance

Using .then().catch()

const hastebin = require("hastebin-gen");

// You can change the extension by setting the extension option
hastebin("code", { url: "https://paste.example.com", extension: "txt" }).then(haste => {
    // Logs the created hastebin url to the console
    console.log(haste); // https://paste.example.com/someid.txt
}).catch(error => {
    // Handle error
    console.error(error);
});

Using async/await

This is assuming that you are in a asynchronous scope

Understanding Async/Await

const hastebin = require("hastebin-gen");

// You can change the extension by setting the extension option
const haste = await hastebin("code", { url: "https://paste.example.com", extension: "txt" });

// Logs the created hastebin url to the console
console.log(haste); // https://paste.example.com/someid.txt

hastebin-gen's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Promise { <rejected> Error: Forbidden

js const hastebin = require("hastebin-gen"); if(interaction.customId === 'sure-yes') { await interaction.channel.messages.fetch({limit: 100}); hastebin(${interaction.channel.messages.cache.map(msg => **${msg.member.user.tag}** => ${msg.content}).join("\n")}, { extension: "txt" }).then((haste) => { let ChannelLog = bot.channels.cache.get(rotex.logsticket) let LogEmbed = new Discord.MessageEmbed() .setAuthor(interaction.guild.name + ' | Log', interaction.guild.iconURL({dynamic:true})) .setTitle("**Action: Deleted.**") .setColor("RED") .setThumbnail('https://media.discordapp.net/attachments/831158984517877836/1029915739072770181/HL_LOGO_SSS2.png?width=676&height=676') .setDescription(Channel: ${interaction.channel.name}
Transcript: Click Here) .setFooter(interaction.guild.name) ChannelLog.send({embeds:[LogEmbed]}) interaction.channel.delete(); }) }

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Error: Service Unavailable

Hey,
I'm always getting the error: "Error: Service Unavailable".

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

It sometimes work, some times dosen''t.

I have a problem that it sometimes work to post into hastebin, and sometimes doesn't. no error logged.

Error: Unauthorized

CODE:

const hastebin = require("hastebin-gen");

// You can change the extension by setting the extension option
hastebin("code", { url: "https://hastebin.com", extension: "txt" })
  .then((haste) => {
    // Logs the created hastebin url to the console
    console.log(haste); // https://hastebin.com/someid.txt
  })
  .catch((error) => {
    // Handle error
    console.error(error);
  });

Error:
Error: Unauthorized at module.exports (D:\Programming\Projects\Botie\node_modules\hastebin-gen\src\index.js:17:24) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

doesn't work

Doesn't work when trying to generate, no errors or anything

An in-range update of snekfetch is breaking the build 🚨

Version 3.5.9 of snekfetch was just published.

Branch	Build failing 🚨
Dependency	snekfetch
Current Version	3.5.8
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

snekfetch is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Service Unavailable

Hey,
I'm always getting the error: "Error: Service Unavailable".

Service Unavilable (error message, discord.js)

Hello

try { const haste = await hastebin("MY CDE", { extension: "txt" })
  message.reply(haste)
    } catch (err) {  message.channel.send(err.message) 

  }

This returns Service Unavailable