What are Sylius/Sylius-Standard and
Sylius/Sylius projects?
Installation guide leads to Sylius/Sylius-Standard and http://demo.sylius.org/ shows Sylius/Sylius-Standard.
So what is Sylius/Sylius?
Sylius Standard uses all the components as add ins (through composer). This means you'll build your app using the sylius components you want.
Sylius adds all the components to the src directory so you can modify the components yourself if you want to. It's a prebuilt app with the Sylius components already in there.
That's what i think anyway. I've been using the Sylius project for the last 6 weeks and it's been incredible. Was a steep learning curve as i was unfamiliar with symfony.
Sylius/Sylius - is Sylius CORE
Sylius/Sylius-Standard - is what you need for starting new project
Sylius/SyliusDemo - is prod example of Sylius DEMO
Related
I am asked to target ESNext modules on my Nuxt app, how can I do that? I could not find anything on the web.
Related to this issue: https://github.com/solana-labs/wallet-adapter/pull/107#issuecomment-939443776
Looking at the freshly released Nuxt v3 beta, we can see that ESmodules are only partially supported in Nuxt2.
You should probably wait/upgrade to Nuxt3.
checking the documentation itself, I found no reports of support for ES Modules, however, it is known that "vitejs/vite (vue)" and VueJS 3 via Command Line support these modules, I believe the Nuxt community needs to create a project template with this setting is built into the project settings.
How to setup MichaelMackus/SyliusSubscriptionBundle in Sylius 1.3
I have already setup this repo
but I don't know how to make product subscribable from the admin dashboard.
This implementation is for Sylius v1.0, a lot has been changed now.
I want to see this work for either version of sylius.
I had a look into the bundle once and came to the conclusion that it never worked. I might be wrong but for sure I can say, it will not work for 1.3 because Sylius migrated to Symfony Flex.
It accesses properties which are not there nor will be implemented by the bundle like OrderItem::getSubscription() used here but is not defined.
There is an PR on Github to integrate this bundle into Sylius and takes care of the aforementioned issue but the PR is outdated as well.
I assume you have integrate Subscription on your own.
Is there a tutorial somewhere that shows you how to install & build Aurelia MANUALLY in Visual Studio 2017?
Why do this?
Ideally I'd like to use bundleconfig.json for as much as I can and
use gulp for those things I can't do in bundleconfig.json.
I'll learn every aspect of the build/bundle/package process as possible instead of having a tool set that up for me. (Makes things
easier to troubleshoot if I know how it is all setup.)
I won't be dependent on CLIs and packages that are not kept up to date. (Several that I've looked at are based on VS 2017 RCs).
I've tried several CLIs and "skeleton" projects but they all have their issues. Some haven't been updated to use the latest csproj.
Aurelia CLI: Project/Folder structure doesn't mirror any standard way of building SPAs that I've seen. Also doesn't mirror what you get when using Aurelia's own "Skeleton Project."
dotnew new spa templates: Though the most promising it's typescript only and not ES6. (Maybe there is a way to switch it easily?)
Aurelia's Skeleton Projects It adds dependencies that I do not need. It also does not work out of the box.
So here is what I've determined since originally writing this question.
My original thoughts with lessons learned:
Why do this?
Ideally I'd like to use bundleconfig.json for as much as I can and
use gulp for those things I can't do in bundleconfig.json.
Answer: I was only doing this because I was trying to embed Aurelia inside of a web api project in Visual Studio. I recommend you don't do this and instead keep it as a separate project. (Separation of concerns)
I'll learn every aspect of the build/bundle/package process as possible
instead of having a tool set that up for me. (Makes things easier to
troubleshoot if I know how it is all setup.)
Answer: Though building from scratch would help me learn about this more it isn't a major roadblock. I was just inexperienced with more modern UI frameworks and their corresponding build processes. (RTFM)
I won't be dependent on CLIs and packages that are not kept up to date. (Several that I've looked at are based on VS 2017 RCs).
Answer: - That happens no matter what route you go. You can wait for a library to mature more if this is a big concern.
The bottom line is my question was based on some incorrect thinking. If you are trying to go this route you really need to ask yourself why and determine if it is worth it. To me it was not. Just go with what works, learn and move on. Oh and don't resist Typescript!
npm install aurelia-cli#0.30.1 --global
create new vs solution in 2017 (ASP.NET Core Web App)
with command prompt, cd into the solution root dir (not wwwroot)
au new --here
select RequireJS or SystemJS (my personal preference)
select option 2, asp.net core
select the remaining options.
Run f5 in VS2017.
Finally, I start to work with Aurelia. There is a starter kit available Here which facilitates initializing Aurelia. But it is a template which should be used within a Web Site template.
I have a pre-configured WebApi project and I want to use Aurelia in it. I've just added the starter kit files and folders to my project. But unfortunately it shows 27651 errors fo files in jspm_packages.
What am I doing wrong? Is there any Nuget bootstrapper for Aurelia available?
Start with the aspnetcore template from Here
You can use web api from the template.
You will be up and running in minutes.
If you are using Web API, starting from an MVC5 project might be faster.
The following link is an Aurelia starter kit with MVC5.
You will have to update it to the latest version of Aurelia, but I managed to make it work with web api 2 and oAuth authentication.
https://github.com/rmourato/Mvc5-Aurelia
A tutorial can be found here.
http://ruimourato.com/2016/01/26/running-aurelia-on-mvc5.html
Hope this helps.
Well you asked what the errors are from. First thing is that you should exclude the jspm_packages folder from VisualStudios solution explorer Right click on it and mark 'exclude from project'.
Next, setup your project on source control (git) if not already and add the following to your git .ignore file
jspm_packages/
node_modules/`
I would suggest creating a second project aside from your WebAPI project that can contain static html, css and js files and do your Aurelia application there separate from your Web API project but in the same solution.
I could possibly give you a solution that is already setup, that shows how to use web api along with aurelia. But it would take some time for me to setup.
For all of my projects using Aurelia, I use the aurelia-cli which you get through npm and I would also recommend this approach.
You can be up and running with hello world in under 5 minutes.
You will then be able to build all the appropriate bits and pieces to talk to your api.
http://aurelia.io/hub.html#/doc/article/aurelia/framework/latest/the-aurelia-cli/1
Any suggestions of how to structure my solutions when developing custom Modules and frontend?
I.e. Should I just clone the repoy and add my modules and change web.config with transform files directly in the repo. Will a future pull working well then? any ideas for simple developing and simple upgrade?
Or is it wrong aproach. Should i use azure deploy script/ slot settings and call virto api to add virto modules...
ok i saw thar virto has updated its documentation
http://docs.virtocommerce.com/display/vc2devguide/Developing+a+custom+solution