yalc | Work with yarn/npm packages locally like a boss | Build Tool library

I have an application built with NextJs (and React) and mobx-state-tree (but could be context or redux) as a package manager. All the stores are created and handled in an npm package called SMK (state management kit) that I created to make the sub-stores reusable in my mobile and web application.

How it works:

1. Create the sub-store with models, actions and views on the SMK and export it as a module.
2. Add the SMK using yarn add @my-repo/smk.
3. Create the root store in my app and import the sub-store from SMK as a child of the root store.
4. Build and start the app and everything is working well.

But I need to run and publish the SMK locally to make it easier development. The solution I used to use is yalc.

Using yalc and running it locally this is the process:

1. In the SMK, runs yarn start. (This will do nodemon --ignore src/index.ts -e js,ts,tsx,json --watch src/ --exec yalc push --scripts)
2. In the APP, runs yalc add @my-repo/smk. (This will add a dependency like "@my-repo/smk": "file:.yalc/@my-repo/smk").
3. In the APP, runs yarn build and then yarn start

And voila! Everything is working perfect, any change I did locally on my SMK is working perfectly on the APP.

BUT, when I run yarn dev that do next dev as default of NextJs it doesn't work.

This is the error I'm facing:

Error explanation: As I only added the setTestingState and testingState locally, it's saying that it doesn't exist.

Possible reason: The fast refresh is not refreshing the cache properly.

I've tried:

• Add // @refresh reset to force it, but didn't work.
• Stop and start the application.
• Build, start and then run dev. (works for build and not for dev)

What is the solution/workaround to solve this issue with yarn dev and yalc?

Windows 10 Docker Desktop on WSL2

Goal: serve an angular app from my devcontainer over my local network (specifically for testing on mobile)

Reproduce:

1. Create a hello world angular application in a clean git repo
2. clone the repo into a new devcontainer (Typescript/Node)
3. serve the applcation

Things I've tried (and every permutation herein):

• --network=host (Never worked on windows, but thought it might on WSL2 - doesn't)
• EXPOSE 4200
• runArgs: "-p 4200:4200"
• appPort: [4200]
• opening port 4200 on PC firewall
• ng serve --host 0.0.0.0 --port 4200

Additional Information:

• ng serve does allow me to view the site on my host machine
• cloning the repo to my host and running ng serve --host 0.0.0.0 does allow me to access the site over my network (but moving in and out of the devcontainer isn't reasonable)

My current DockerFile is pretty vanilla:

I'm working on an NPM package that is intended for use solely via npx *, a la packages like create-nuxt-app.

Is there a way to test my package with npx *? In other words, run my bin script without installing the package.

I've read this discussion, which suggests perhaps there isn't. I realise I can test the installation, rather than mere running, of my a packge via something like Yalc, but Yalc provides only yalc add *, which simulates npm install *, not npx *.

What's the best approach here?

I have two projects specified in the jest section of my package.json.

Intro: I've generated two projects with vue-cli ~4.2.0:

• parent-app - main project
• dummylib - library which is imported by parent-app. Has a bunch of .vue components inside.

Currently, parent-app works fine in dev mode with dummylib being imported into it. All dummylib's vue-components are rendering ok.

Problem: I want to edit dummylib and see changes on the fly, as it takes place with parent-app: without having to rebuild it after each code modification.

My current library development process:

1. (dummylib): yalc publish - assuming it has been built already
2. (parent-app): yalc link dummylib
3. (parent-app): npm serve - start local development
4. Editing dummylib...
5. (dummylib): npm build - !!! Want to avoid this step !!!
6. (dummylib): yalc publish --push - After this, I see my edits from (4) being applied...

So are there any options to avoid (5)? I've also thought about monorepo, but decided not to have it currently.