Fabio

@brillout Yes this works for me locally. See also - https://stackoverflow.com/questions/8088795/installing-a-local-module-using-npm - https://stackoverflow.com/questions/15806241/how-to-specify-local-modules-as-npm-package-dependencies

> Does it work for all package managers? E.g. Yarn, pnpm, Deno, and Bun. I''l check on that. > One drawback of this approach is that it doesn't eject the...

@brillout I added a new commit and I will need some feedback here on how to proceed. So as I understand now, the goal is basically to eject only dependencies...

@nitedani thanks for the input > We can store extra needed info under the vike-eject key in each extension. This makes a lot of sense and would make the development...

> You can use require.resolve or import.meta.resolve to get the path. I guess, I wanted to get rid of the constraint that the user would need to install the package...

WIth the updated code I now have in my test project:     And inside the test project I imported the component like this:  btw, I usually...

@nitedani or @brillout a review of this would be great, I kinda need some input if this is now what is needed. Then I can maybe clean up the code...

@brillout sorry for not answering, just very busy at the moment. If you really think it makes sense to go forward with the current work. I can finalize a MR....

@brillout alright, yes I have the coding for the level-1 already ready. I updated the code to include only the level-1 support. # How it works: 1. Add the following...

Sure I am following your lead there. I think you are right and it makes sense to have it as a stand alon package since, it is not really directly...