feat(nodejs): add pre and post install scripts with coder exp sync support

[blinkagent]

Description

Add pre_install_script and post_install_script variables to the thezoker/nodejs module, following the pattern established by other registry modules (agent-helper, claude-code, aider, goose, amazon-q, etc.). Scripts use coder exp sync for reliable execution ordering, enabling dependency coordination between modules.

Changes:

• Added pre_install_script and post_install_script optional variables (default null)
• Wrapped install in coder exp sync want/start/complete flow
• Added conditional coder_script resources for pre/post install
• Added outputs for cross-module coordination
• New nodejs.tftest.hcl with 5 test cases
• Updated README with documentation and examples

Type of Change

• New module
• New template
• Bug fix
• Feature/enhancement
• Documentation
• Other

Module Information

Path: registry/thezoker/modules/nodejs
New version: N/A (enhancement to existing module)
Breaking change: [ ] Yes [x] No

Testing & Validation

• Tests pass (bun test)
• Code formatted (bun fmt)
• Changes tested locally
• terraform validate success
• terraform test — 5 passed, 0 failed
• Backward compatible (new variables default to null)

Related Issues

None

[DevelopmentCats]

I have tested this and it works well

Using these exp sync commands the claude-code module can now use nodejs and wait on nodejs before claude-code installs.

The pre and post install scripts are just for flexibility if someone wants to just use the node module, and post install commands to install whatever they would need.

[35C4n0r]

@DevelopmentCats @matifali should we use https://registry.coder.com/modules/coder/agent-helper here ?

[matifali]

@DevelopmentCats @matifali should we use registry.coder.com/modules/coder/agent-helper here ?

I am ok if we had a more generic name for that module. may be script-helper or coder-helper

[DevelopmentCats]

We totally could use that module here instead, I assumed that it was for agents only based on the name but if we are cool making it more generalized I'll go ahead and do that

[35C4n0r]

I assumed that it was for agents only based on the name but if we are cool making it more generalized I'll go ahead and do that

This was the idea I had in mind, but we later discussed that we want it to be usable for general purpose too.

[35C4n0r]

@DevelopmentCats @matifali should we use registry.coder.com/modules/coder/agent-helper here ?

I am ok if we had a more generic name for that module. may be script-helper or coder-helper

If we want to change it, this is the right time to do it. Since none of the modules reference it rn.

[DevelopmentCats]

@DevelopmentCats @matifali should we use registry.coder.com/modules/coder/agent-helper here ?

I am ok if we had a more generic name for that module. may be script-helper or coder-helper

If we want to change it, this is the right time to do it. Since none of the modules reference it rn.

Since we haven't nested this into any other modules quite yet, do you think we are good to just completely remove old tags and rename the agent-helper module then?

If so I will go ahead and start up a PR for this @matifali @35C4n0r

[matifali]

Since we haven't nested this into any other modules quite yet, do you think we are good to just completely remove old tags and rename the agent-helper module then?

Yes