Hi all I m trying to create a workaround for

Question

Hi all I m trying to create a workaround for <https github com pulumi pulumi issues 2661> yarn 2 3 workspaces What are the exact requirements for `aws lambda CallbackFunction`

prehistoric-kite-30979 · Answer

I can get non local workspaces to work e g ` pulumi aws` by symlinking

prehistoric-kite-30979 · Answer

But local workspaces complain with ```failed to compute asset hash asset path node modules tetrateio components aws lambda is a directory try using an archive```

prehistoric-kite-30979 · Answer

the only difference I can see is that my local workspaces packages have no generated javascript

prehistoric-kite-30979 · Answer

the other difference looks like ` pulumi pulumi` is a directory but ` tetrateio components aws lambda` is a symlink

little-cartoon-10569 · Answer

I think they re the same as described in and you can t use inline lambdas that is CallbackFunction and similar mixins unless you also have an already generated node modules in the same directory that Pulumi is bundling into the zip

little-cartoon-10569 · Answer

My workaround is to link the project s node modules into any directory that has a CallbackFunction So long as the CallbackFunction only uses code that is also used in the main project so that the node modules directory has all required dependencies then it works

little-cartoon-10569 · Answer

Aside this has the downside that I can t run my mocha tests from those directories because I can t get mocha to find packages json in a parent directory if it has already found node modules

prehistoric-kite-30979 · Answer

interesting so even when I symlink node modules I see that error ^^

prehistoric-kite-30979 · Answer

but only for local workspaces external packages work fine

prehistoric-kite-30979 · Answer

we used to use node modules symlink and it worked before we migrated to yarn workspaces

prehistoric-kite-30979 · Answer

so its something specific to how yarn handles local workspaces

little-cartoon-10569 · Answer

thinking face

little-cartoon-10569 · Answer

Local workspaces are links from node modules to the workspace right If your workspace contains ts files then the imports won t work If you re compiling to lib based on your tsconfig s outdir then you need lib to be your workspace

little-cartoon-10569 · Answer

The link would need to be node modules myproj gt lib myproj not gt myproj

little-cartoon-10569 · Answer

But I think you can do that in yarn workspaces using the name property

little-cartoon-10569 · Answer

That is myproj package json needs ` name lib myproj ` Completely untested that s derived only from reading <https classic yarnpkg com en docs workspaces toc how to use it>

prehistoric-kite-30979 · Answer

yes local modules are symlinks in the node modules We don t compile to JS anywhere so let me try that

prehistoric-kite-30979 · Answer

compiling js didnt seem to help going to have to give up for now and come back to this sweat smile