Lukas Holzer

Hey, @scottlovegrove, thanks for reaching out. First of all, multiple things are happening here; let me maybe explain to you: We've released a new major (breaking) version that added better...

Sorry for the frustration @South-Paw. Regarding the `.netlify` folder, this is something internal netlify is creating and relying on for storing internal state and build outputs like bundled functions etc....

@jgeringer I would love to understand your use case more on having a workspace, but it seems that the root is a package as well? So while implementing the workspace...

@ForbesLindesay for that there is the `--cwd` command this should not need the `--filter`. So, in your case, `netlify deploy --cwd packages/website/out` should be enough. I understand your request, but...

Instead of using the "non-public" `--cwd` flag you could just set the cwd of your github actions task or CI runnter to the cwd of the monorepo like `apps/my-app` this...

With that configuration, I get even in JavaScript completion for the `Netlify.env` 

@sarahetter yes but sadly never had time to finish it up

@ailadas can you please add more description why this needs to be reverted?

@andreilg thanks for reporting the issue I think @danez has already worked on something like that IIRC.

I'm going to cut a pre-release before merging this and trying to prepare the breaking changes already upfront on the repositories. > Latest RC version is on `@netlify/[email protected]`