This message was deleted Pulumi Community #general

Join Slack

This message was deleted.

# general

sparse-intern-71089

11/09/2021, 4:53 AM

This message was deleted.

miniature-king-36473

11/09/2021, 8:40 AM

pulumi uses a

require

to load the program. This means that all the code which is used must use commonJs and not newer es6 modules. I suspect that the package you are trying to use has not been compiled to commonJs - do you have

"compilerOptions.module": "commonjs"

set in the module you are trying to import? When you say "import a pulumi repo via a github url", are you trying to import the source code? In which can you probably need to build a package and import that (you could use github packages for this)

steep-portugal-37539

11/09/2021, 5:40 PM

Thanks for replying Mark! Yes my module setting is commonjs I am trying to import the local source code into another local repo via an npm install with a git url.

steep-portugal-37539

11/09/2021, 5:41 PM

Is there no way to do this without packaging up the pulumi repo to npm or github pkgs?

steep-portugal-37539

11/09/2021, 5:44 PM

Even if i do pkg it up, i need to set “main” in package.json to be

index.js

, right? Otherwise pulumi won’t be able to run the installed pkg.

steep-portugal-37539

11/09/2021, 5:46 PM

What is the proper development flow then? Bec i’d like to test my pulumi code within the repo itself. Do i need something like nodemon that is going to run tsc on changes? It seems redundant to need this. Pulumi is able to have a .ts file as an entrypoint

miniature-king-36473

11/10/2021, 11:08 AM

Pulumi won't build the code in the module you are installing, so this needs to be built before you do the install. The easiest way to do this is to publish a package with build code from your other repository and then import that. (As an alternative you may be able to use a npm install script to run tsc on the package when it is installed. I have not tried this though) My workflow is to create ComponentResource components in other repositories and publish them as GitHub packages. In these repositories I have an

example

folder where I have a Pulumi program which can create these resources for testing purposes. I then install these packages into other repositories which use these components in different environments. The advantage of this approach is I can keep my components versioned and easily track updates to the environments. The downside is lots of building of packages which can be tedious at times. If you wanted to just reference the source code, you could probably use git submodules to bring the code into the current repository. I have never really got my head around those though and always seen to end up in a mess. YMMV though.

miniature-king-36473

11/10/2021, 11:12 AM

Looking at the docs for npm install - https://docs.npmjs.com/cli/v7/commands/npm-install - it looks like you may be able to add a

prepare

script that npm will run when you do an

install

for a git url. This could run

tsc

to build the code from the repository so that Pulumi can use it.

steep-portugal-37539

11/10/2021, 9:07 PM

Thanks Mark 😃. I ended up doing the postinstall script. And just installing the module via a git url. Soon I will actually publish to npm.

miniature-king-36473

11/11/2021, 9:00 AM

great to hear it worked... Something I may use in the future - would be a good way of speeding up workflow

164 Views

Open in Slack

Previous Next