refactor: set up monorepo #554
Conversation
| # THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY. | ||
| # yarn lockfile v1 | ||
|
|
||
|
|
There was a problem hiding this comment.
hm how did this end up here? can you revert it
There was a problem hiding this comment.
was using this to break the cache. fixed 88b994a
| "files": [ | ||
| "dist/**/*" | ||
| ], | ||
| "resolutions": { |
There was a problem hiding this comment.
should we move resolutions for runtime dependencies to the package's package.json?
There was a problem hiding this comment.
I was thinking it would be nice to have them shared among packages, but I guess it's probably better to just deal with issues individually if they come up. so i moved the resolutions down to the sdk package 88b994a
There was a problem hiding this comment.
oh actually, those are all there for audit-ci fixing purposes, so we want them there c80b628
| import * as path from 'path' | ||
|
|
||
| export const loadEnv = () => { | ||
| dotenv.config({ path: path.resolve(__dirname, '../../../../../.env') }) |
There was a problem hiding this comment.
will this work properly both in the case when you're running commands at the root level of the monorepo, and when you cd into the package and run it there?
There was a problem hiding this comment.
it does work from both locations. __dirname is the location of this file.
2 participants
packages/sdkand move its unique config therescriptsfolder in a future PR