Cannot test locally committed code to Node.js in my PC.

[ayan-de]

Node.js Version

v20.15.0

NPM Version

10.8.2

Operating System

Linux ayan-de 6.5.0-45-generic #45~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jul 15 16:40:02 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

buffer

Description

I just cloned my node.js forked repo and I have built it using ninja following the guideline resulting creation of a node binary file in my repo. I made some commits in the source code but how will I test if my code is running fine or not? I want to run my new committed source code. Can anyone help me with this? I have followed all the steps involved in BUILDING Nodejs and am not sure if my built was perfect or not (how would I know that?? )

Minimal Reproduction

No response

Output

No response

Before You Submit

• I have looked for issues that already exist before submitting this
• My issue follows the guidelines in the README file, and follows the 'How to ask a good question' guide at https://stackoverflow.com/help/how-to-ask

[preveen-stack]

After the build process completes, the Node.js binary will be located at out/Release/node.

[ayan-de]

yes it is present there! now how will i test my code??
Like i have made changes how will i run it to see if the function is working perfectly?

[preveen-stack]

I guess you mean the command, right?
./out/Release/node script.js

[ayan-de]

after every time i change the code will it get reflected in this ./out/Release/node or i have to make it again ?

[preveen-stack]

You have to rebuild after every change

[ayan-de]

btw this is how i am running it copy.js file is at another location

[ayan-de]

Thanks its working

[preveen-stack]

https://github.com/nodejs/node/blob/main/BUILDING.md#installing-nodejs

Check this if you want to replace the system binary with your custom version