Help with @paths configurations

[codeedog]

Struggling with the proper formation for @paths in two situations and could use some advice. I'm not sure what keywords to use to search for possible answers on the interwebs, so hoping to get some help here.

1. I have an angular app (admin-ui) using the environments/* configuration files for development and production. I'd like to fetch the environment file using the @ feature for import, but cannot divine the magic configuration for tsconfig.json. I don't want to use '../../environments/environment' in my code, preferring '@Environment', for example. However, as I couldn't get the latter to work, I instead placed a path for '@admin-ui/environment' in the tsconfig.base.json file in the root directory. This feels wrong for many reasons, mostly because no other app requires that environment file. I'd like to move that path declaration down to the admin-ui's tsconfig.json file, scoped to where it belongs.
2. I have an AWS Lambda app I'd like to test. Because no aws generator exists for CDK or AWS or anything like that, I generated a node application and then modified it for my purposes. I've made minimal changes to the apps configuration files. I am using jest for testing and have a set of tests. I'd like to use @ paths here, too. However, I just cannot seem to figure out how to formulate the proper pathing to reach my various files. Some of this appears to be unique to jest, which has made it even more challenging.

If anyone has advice for @ paths in app modules for regular usage or test (jest), I'd appreciate it.

PS: Just want to add that I really like nx and the entire monorepo concept. I've been coding within the structure for a few months now and it feels so much better than trying to coordinate data touchpoints between various repositories. In addition, I have one place I go to to do all of my work. I'd like at some point to try to formalize the CDK applications I've built into a generator, but there's so much to learn (related to AWS) and there are some missing pieces in that environment that are still waiting for production quality (like the ability to invoke backend code locally; it's possible in regular server style, but with CDK - the AWS answer to IaaS - they still don't have it working yet).

If anyone is thinking about a CDK AWS generator, please let me know. Happy to brainstorm, give feedback, maybe do a little coding and definitely test.