Has anyone had success using SST as part of a larg...
# help
a
Has anyone had success using SST as part of a larger yarn workspace project? For example, I'd want my SST workspace to have access to the "shared" package in a directory similar to below. This is slightly different than this example where all of the workspaces reside in the SST directory
Copy code
/sst
  yarn.lock
  package.json
  [...]
/shared
  yarn.lock
  package.json
  [...]
/backend
  yarn.lock
  package.json
  [...]
yarn.lock
package.json
t
With the way SST works today, sst.json has to be at the root of your project
Is there a reason you have multiple yarn.lock files?
a
i see -- thanks! Yeah, the multiple lock files are because i'm using the --no-hoist option.
I wanted to see how it would fail so I tried putting
sst
as a workspace (not in the root, but as a sibling directory to my shared package) and as I expected it worked fine locally. But it deployed with the error
Copy code
No eslint config found. There was a change starting in SST v0.48.0 with the eslint integration for better editor support. Please add the following to your package.json:

"eslintConfig": {
  "extends": ["serverless-stack"]
}

For more information check the documentation: <https://docs.serverless-stack.com/working-locally#linting--type-checking>
There was a problem linting the source.
There was an error synthesizing your app.
error Command failed with exit code 1.
t
yeah that's something you need to add if you don't have lint: false in sst.json