monorepo | A monorepo for my old NPM libraries | Blockchain library

Is it possible to an Expo app example to load a module located in the parent folder AND to see changes in the example app when i rebuild the package (with tsc -w to rebuild on any saved files)? I precise that the module is not publish on npm yet.

I've already succeed to do that using monorepo architecture with yarn workspaces and expo-yarn-workspaces package. But what about the case when you don't want to publish your package like a monorepo?

For example, in this repo https://github.com/cuvent/react-native-vision-camera There is an example RN app in bare workflow and in its package.json there is no mention of the developed package (meaning that it's not installed like a normal dependency). But in the app src/App.tsx, the package is used like that :

I have a Yarn monorepo (workspace) with 2 packages: backend (Node.js/TypeScript) and frontend (React/Typescript).

/package.json (trimmed)

We use Angular in a nx monorepo in which we have been using Capacitor 2.4 for half a year now. We only use the android platform as of now. Now, we need to upgrade to Capacitor 3.0. The app itself is running again, however, as soon as I use any Plugin I always get the following exception: ERROR Error: "Device" plugin is not implemented on android

This is the same for every Plugin I have tried to use. So, if I would use the Storage Plugin I would get the same exception only for "Storage". I have followed the Capacitor migration guide (https://capacitorjs.com/docs/v3/updating/3-0) in detail, but I can't figure out where I went wrong. In general, the app works now, as long as I have any code that uses a Capacitor Plugin commented out. The code using the Plugins did work before the upgrade.

As according to the migration guide, I added import '@capacitor/core'; at the main.ts file, although I also tried putting it in the app.module.ts but had no success there either. I have installed every plugin for the whole app (the root) and for the nx-capacitor app (the capacitor app added with @nxtend-capacitor) as suggested here https://nxtend.dev/docs/capacitor/getting-started/. I also have updated the capacitor cli, the capacitor core and the capacitor android version for both package.json files. Furthermore, according to the android upgrading guide, I have also updated gradle and the android gradle plugin. I have also updated the Android variables accordingly.

I honestly do not have too much experience or in-depth knowledge of Capacitor and I am aware that Capacitor 3 is still in Beta as of this point. However, maybe someone has already stumbled upon this problem and found a solution. I am also not sure, if this problem could somehow be caused by using this monorepo approach with nx. Has someone had experience in upgrading Capacitor to 3.0 while using a Nx monorepo?

For reference, this is the current package.json for the capacitor app:

It's possible to set the working directory for separate scripts:

How to detect which tests pytest need to run?

Up to now I run all tests in CI. This is slow.

Isn't there a way to automatically detect which tests need to run, and only execute a fraction of the whole test suite?

Background: I am reading the Google SE book and read about their gigantic monorepo and that their tool Blaze can detect which tests need to run. Sounds very cool.

I'm using react-app-rewired & customize-cra to setup a multi-project monorepo with shared TypeScript code, without ejecting from create-react-app (the setup is described in this answer). The layout is like:

In a lerna monorepo, babel is installed only at the root package level. When running npm exec babel-node from root/packages/packageA, it fails with:

npm ERR! could not determine executable to run

From the same directory, running npm run test, where test is just set to babel-node opens the babel-cli.

I.e. why can npm resolve the path to the root node_modules' bin when run as a script but cannot when run from the terminal directly?

EDIT:

I.e. https://github.com/bishonen/newproject/tree/master/packages/someapp

when running npm run test-babel, it will work from any of the 3 directories which contain a package.json. When running npm exec babel-node, it will only work from the root directory.

So I want to create shared libs in my angular project. I have listed down below my two approaches, which both do their job, but I don't which is the better one, that I should implement.

I'm using the code-first approach to GraphQL with NestJS and have a monorepo setup using Nx.

The schema.gql is only produced when I run the server, which I can't do during CI. It's impractical for me to copy the whole repository into the docker image and start the server. The schema.gql isn't generated when you build the nest application.

I've also looked at Generating the SDL manually doc on the NestJS website, but not really sure how to integrate that script.

Just wondering if someone has managed to generate the schema without starting the server?