common-component | this a folder for introducing the components | Frontend Utils library

So I have inheritied a program (APPLE) whose code baseline originated on another program (ORANGE). In order to make it easier for multiple teams to update this code we are moving the 'common' stuff out into a Shared Project (TREE). So far, we have made this work great with pulling out the Models and Controllers to a Shared library (obviously a few Models/Controllers remain in ORANGE as they are specific to that application).

However, I'm hitting a wall on how to extract the Views. The idea would be that the Shared Library (TREE) contains the common views (like file import, and landing page) while leaving the program specific code behind in the 'main' ASP.net application (APPLE/ORANGE).

I found this article which looked really good. Except 1) I don't have Microsoft.AspNetCore Nuget (My Microsoft.AspNet.[package] don't appear to have ViewComponent), 2) When creating a new Web MVC project, it doesn't have a wwwroot, Program.cs, or the .json files. I also found another article talking about using VirtualFiles, but it doesn't really indicate where the EmbeddedResource class would reside, and (I could be mis-understanding) but it seems to look for all the Views in the vitural location.

So what is the best way to split common views out into the Shared Project I've created and utilize them in our program application?

This is an ASP.net application using MVC. It is not a Razor application.

I have access to Microsoft.AspNet.(various packages) and DevExpress.(various packages), but must go through a process to obtain other packages (so I can't easily download a package and test out suggestions).

I have the parent project "giftcard-service" which I use only to build. All the code is in the module which is named "giftcard-service-main". I'm able to build (clean install) giftcard-service but not able to deploy/run it, which we do by mvn spring-boot:run command.

Since this is an enterprise/company project I would restrict some information for obvious reasons.

This is the error I get on console.

I have an npm package for common components hosted on an internal git server. For some reason when I call npm install in another project I want to consume this in it will not run the prepare hook. Obviously, this does not work since the npm package needs a /dist folder in node_modules to be able to consume the package.

I have already tried things such as using the deprecated prepublish hook and even that does not get called. I also tried to do postinstall to see if I could build after install, while that hook did get called it failed because the devDependencies were not installed

package.json

I have a requirement where I have a login page which has just the login component. Once a person logs in, the user gets to page having a left navigation and a component on the right. With the help of this left navigation, a person can navigate to different components.

So the thing is, the left navigation component should be available on all the pages once logged-in and not on the login page.

I tried to replicate the same at https://stackblitz.com/edit/angular-common-component-in-named-router-outlet but it just loads the navigation component. The router configuration looks like

I am creating a package that contains common components that we created on the company I work for, and we want available for all projects. We use TypeScript, and I moved the code to a new project and I am able to publish to npm and add the package in the dependencies section of one of my projects. However, when I try to use it I get a compile error saying

error TS2604: JSX element type 'Loader' does not have any construct or call signatures.

my code (simplified) looks like this:

I have a React Native application that I upgraded. Back when it was legacy, if you went to a news article and the article had hyperlinks and you clicked on the hyperlinks it would redirect you to your phones browser and open the link there, but it no longer does that because we had to upgrade the react-native-autoheight-webview library, so the patch that was done for the 0.6.1 version is now gone. That patch is what allowed hyperlinks to open in a separate browser.

I have been trying to repeat the process so we can get the same behavior. So I added this code to node_modules/react-native-autoheight-webview/AutoHeightWebView/index.js file:

I am trying to write tests for my application using Jest, but I am facing the same issue for every functional component that uses React Hooks.

This is my package.json file, but I can't see what might be wrong with it.

I am noticing that the error is occurring on the line: { provide: AppConfigService, useClass: MockAppConfigService },, not inside any tests. In fact, I can set breakpoints in chrome at the first line inside of each beforEach and ìt (at TestBed..., fixture..., and expect...), as well as entirely swap out my component for a dummy AltTestComponent, and it still fails with the same error before reaching a breakpoint. At that point, the only reference to AppConfigService at all is in the { provide ... } statement.

There is a screen called Login that is passing in an action creator from loginActions like so:

https://gist.github.com/ldco2016/e2feedc5460e64e9b740af73cec5fe89

When I boot up the application and click on the Login button, I get the following error:

In the legacy version of the application, all this was working, no such error, but now when clicking the Login button in the upgraded 0.60.4 version, I get this error.

When I look at the loginActions file, I am wondering if there should be an export default connect()() and mapDispatchToProps in there to inject props into Login screen. So one of my questions is, do I indeed need this?

How did it work before? Was it passed down from the parent? This is the loginActions.js file: