Custom extension (node) - Raise Exception (throw error) step by Karh/Apple

Wappler Extensions
1

THIS FUNCTIONALITY HAS NOW BEEN INTEGRATED INTO WAPPLER.

Not my extension, produced by @karh via Claude AI, i agreed to publish this as an NPM on his behalf
Obviously i am not in a position to support this extension

Details in this post

(Raise Exception (throw error) step)

Extension can be found here.

3 Likes
2

Is it just me or there's no code?

image
image1568×418 34.5 KB

Btw, can you also update the code to:

exports.throwError = async function (options) {
    options = options || {};
    const message = this.parseOptional(options.message, "string", "Custom error thrown from the extension");
    throw new Error(message);
};

It was missing expression parsing

3

Sorry @Apple, forgot to copy files from dev to production.

uploaded 1.0.2 with files attached.
Also made two minor adjustments to the HJSON adding missing elements.
To be honest, have not tested changes but sure they will not cause issues :crossed_fingers:

I have not touched the code as this is @karh work, will only do that if he OK's it.
(I just uploaded to NPM for him.)

4

Change of heart as i may need this myself.
Just going to.update as i assume kahr isnt going to reply.

Should really have noticed that myself although not sure how often people would add parameter as a dynamic value but picker is available so module should handle it.

Will upload amended code as 1.0.3 in next few hours

5

version 1.0.3 with enhanced code uploaded

6

Been on holiday! Thank you Brian, please do take it over.
Would love to take credit but it was literally a single prompt for Claude that resulted in the code.

So please go ahead :smiley:

7

My brain might still be left on a mountain somewhere but shouldn't it be putting the throw-error.js and .hjson files in my /server_connect/modules folder?

I deleted the ones that I made originally, did the npm install command and can see that it's added to my package.json but it's not usable yet.

8

for development yes, you are correct, they go in extensions/server_connect/modules folder

But if you develop multiple extension you need to separate them out before uploading as npm so the correct files are uploaded. This is the recommended technique

9

I mean from the user perspective now - I'm not getting the files in there after running npm i wappler-raise-exception-throw-error

Any clue what's up with that?

10

Have you installed via the installation manager as outlined in the post i shared above?

11

Using the wappler settings? No, I'm traumatized with saving project settings as it overwrites important stuff.
I'll just manually copy over the files, thanks :smiley:

12

then you should be able to just leave the files in the extensions folder and it should work, no need to use NPM to install. Using an npm is really about sharing.

There is currently an issue with PHP extensions and Wappler doing it that way but i assume you are using node.

1 Like