No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@U03E6AMK5AP> you can set the package name in the schema

<https://github.com/jaxxstorm/pulumi-aws-securebaseline/blob/3d7ba9f567f29f3be2658a6ad4811e34bdbce496/schema.json#L135|https://github.com/jaxxstorm/pulumi-aws-securebaseline/blob/3d7ba9f567f29f3be2658a6ad4811e34bdbce496/schema.json#L135>

<@UCWG26BH7> thanks! This took one step further at least:)
I'm struggling a bit with the build and test step `make install_nodejs_sdk` . It's returning this:

```&gt; @easee/cp-pulumi-component-package-xyz@${VERSION} install
&gt; node scripts/install-pulumi-plugin.js resource xyz ${VERSION}

[resource plugin xyz-0.0.1] installing
error: [resource plugin xyz-0.0.1] downloading from <https://github.com/easee/cp-pulumi-component-package-xyz/releases/download/v${VERSION}>: 404 HTTP error fetching plugin from <https://github.com/easee/cp-pulumi-component-package-xyz/releases/download/v0.0.1/pulumi-resource-xyz-v0.0.1-linux-amd64.tar.gz>

There was an error installing the resource provider plugin. You may try to manually installing the plugin by running `pulumi plugin install resource xyz 0.0.1````
Do I need to deploy an initial release to do local testing? this seems a bit strange

yes thanks. I've tried doing this with this command: `export PATH=$PATH:$PWD/bin`
It might be because I instruct bash to be used as the shell in the makefile. The pushd command is not working if I run the make build commands without this

I usually do:
```export PATH=$PATH:$(pwd)/bin```
like you, then use `yarn link @jaxxstorm/packagename` inside the examples directory

Thanks. I have switched the yarn commands to npm since we use this in my org. I can run "npm link" in the sdk/nodejs folder to make `npm link @easee/&lt;packagename&gt;` work in the examples directory, but this does not seem to be correct. The pulumi up command in the examples directory returns this:
```failed to discover plugin requirements: illegal semver returned by language host: easee/pulumi-aws-xyz@v${VERSION}: Invalid character(s) found in major number "${VERSION}" ```
Since the `make install_nodejs_sdk` fails I guess this is part of the reason the VERSION is not populated correctly. I've defined VERSION both in the schema and as an environment variable