In the last post I wrote, I had a first look at a plain, clean, and lightweight React setup. I’m still impressed how easy the setup is and how fast the loading of a React app really is. Before trying to push this setup into an ASP.NET Core application, it would make sense to have a look at the ASP.NET Core React project.
Create the React Project
You can either use the “File New Project …" dialog in Visual Studio 2017 or the .NET CLI to create a new ASP.NET Core React project:
The last two years, I have worked a lot with Angular. I learned a lot and I also wrote some blog posts about it. While I worked with Angular, I always had React in mind and wanted to learn about that. But I never head the time or a real reason to look at it. I still have no reason to try it, but a little bit of time. So why not? This post is just a small overview of what I learned during the setup and in the very first attempts at using React.
If you’re having troubles with organizing your API for a Node.js app, using the Sails.js framework with GraphQL, know that you’re not the only one – we’ve been there too.
Since this is not an every-day combination of technologies, it was challenging to define the anatomy of such an app and its tests, but we did it!
Before I started to use Stencil, I worked a lot with React (and am still working with the library). While developing React components, you often need to use a render prop, so I wanted to see how it would work in a Stencil environment. As you might figure, it works in Stencil and this gave me the idea to write a short post to explain how to use the render prop in Stencil.
A render prop is just a name for a simple technique in which you pass a function to a component which will be used in the component render function. The reason to use a render prop is the ability for a component to share its inner state without exposing it to the outside.
If you’re a Vue developer, you’d benefit from learning all these new features. But as a means of triage, you might start with those features that apply to Vue specifically.
For those who haven’t used it, Yeoman is a scaffolding tool designed to help kickstart new projects by running scripts called generators. Generators are often used to create opinionated starter apps with best practices and build scripts built in. The JET generator installs a sample app and includes a Grunt-based build system that can be customized as needed.
With the recent announcement that Node.js is generally available as part of Red Hat OpenShift Application Runtimes, I wanted to see how easy it was to deploy an Express.js app on OpenShift.
Before we start, there are some required prerequisites. You need to have Node 8.x and npm 5.2 or greater installed. npm comes with the official node distribution, so if you install Node from Nodejs.org, you should be good.
Without CSS transitions, the transform property is only able to turn over the object it is applied to. So, in most real-life situations (real-life?), these two options are applied together.
The powers which this property posses are:
I love lists. I keep everything I need to do (too many things, usually) in a big to-do list, and the list helps keep me sane throughout the day. It’s like having a second brain!
There are hundreds of to-do apps out there, but today I’ll show you how to build your own from scratch. Why? It’s the perfect exercise for learning a new language or framework! A to-do app is more complex than “Hello World”, but simple enough to build in an afternoon or on the weekend. Building a simple app is a great way to stretch your legs and try a language or framework you haven’t used before.
In the current era, most software development companies work in a collaborative environment where several developers contribute to the same source code. While some will be fixing bugs, others will be implementing new and different features. The problem arises, how do you maintain different versions of the same code base? This is where the branch function shines! Branch allows each developer to isolate his/her work from others by creating a new branch from the original code base.