I am trying to setup Discord-components in my vuepress 2 project. But i have no clue how to do it.
Discord-components link: https://github.com/skyra-project/discord-components
Related
I am building a Nuxt 3 SSR application, which I'm getting rather familiar with. What I can't wrap my head around, if it's even possible, is to have a single Nuxt project for multiple domains. For example, I have a few websites such as websitea.com, websiteb.com, websitec.com, and want to keep pages separate, while sharing components, compostables, etc. I'm not sure if this is possible, but it would be greatly appreciated if anyone has any advice.
I had this requirement too and came up with this solution:
Everything is shared as one Nuxt 3 app with a single nuxt.config.ts. The only difference is that each app has it's own sub-directory within /pages.
Here's how I set it up:
Create a pages structure like this:
/pages
--/website1
--/website2
--/website3
Define an env variable like WEBSITE_ID (e.g. within your project's .env)
WEBSITE_ID="website1"
Inside of nuxt.config.ts add this configuration:
export default defineNuxtConfig({
//...
dir: {
pages: `pages/${process.env.WEBSITE_ID}`
},
//...
})
When it's time to deploy your apps, inject the corresponding WEBSITE_ID env variable for each at build time.
While in development, simply edit the WEBSITE_ID within the .env to switch which website you're working on.
This setup makes it so that for example, when website1 is active, pages/website1 is treated as the /pages directory... so pages/website1/index.vue would be resolved when requesting /.
One of the solution would be to create a library using Nuxt Kit. This library will contain all of your components, composables and everything you need to share between your projects. You will need to add your library as a dependency of your different websites.
If you don't want to deal with multiple git repositories you can create a monorepo. (For example using pnpm: https://pnpm.io/fr/workspaces)
So, I have inherited a Laravel 8 project from the previous developer who decided to leave for a greener pasture. And I see all this blade components everywhere, (x-this, x-that) and I have also created a few. I have used make:component command and I can see the components being generated both in `App/Views/' and 'resources/views'. That's great.
Now, there are other components, which the previous developer have created that I can't figure out where where these components are being registered at. They are not in the App directory, not in the service provider boot, there's no custom vendor in the composer.
So, I think the obvious question is, where else should I look for?
Those may be anonymous components. Anonymous components does not require any registration. So check resources/views/components folder.
For more info:
https://laravel.com/docs/8.x/blade#anonymous-components
Is a good practice work Vuejs with a unique .js file (all logic there) with a cshtml? like angular 1.0.
Happen that i need mix .net core action controller with Vuejs, it is not a vuejs app, I want use vuejs as my tool to refresh the content.
I created a template that combines .NET with Vue.js. You can use it as a starting point or an example.
GitHub: https://github.com/danijelh/aspnetcore-vue-typescript-template
I am getting error while using shared service in angular 2.
I just added in provider and trying to inject in another component giving me issue.
Could you please help me??
Thanks.
Only one component can bootstrap throughout the application. You are trying to bootstrap a service. Add the service in the providers. Then it'll work fine.
I'm working on a web application that consists of two separate modules. I've finished working on module 1 of the application and right now I'm starting to work on module 2. I need to find a way that allows me to deploy the two modules separately at the customer.
For example, when doing changes to module 1 I would deploy module 1 only, when adding new features in module 2 I would deploy module 2 only.
I currently have a single project in my application which includes module 1:
should I create a new project for module 2? If so, I'm not sure how I can create a link between them, as I will need to navigate from Module 1 to Module 2 using an aspx page or so.
If I let them be in the same project, would that be a good design practice? Also Is there a way to still separate between the deploys?