ReactJS Seed Application: Why Not Start with the Real Deal?

#ReactJS seed application: Why not start with the real deal?

  • Looking at the most common React seed applications you will see that they have, for each component, a custom folder and they group them all as components.
  • Everyone knows if you google for “React seed application” or “React boilerplate” you will find tons of prebuilt seed applications out there, some of which are being used by thousands of people.
  • Selecting Browserify as our initial stack is a very good example of why a seed application can be useful.
  • After looking at these, we found that though a lot of them offered unique and interesting concepts, none of them seemed very scalable to us for use in large web applications.
  • For one, a seed application allowed us to try out different libraries and project structures without the restriction of a particular use case.

Hyperwallet’s Software Development Team Lead looks into tools for building their final browser version in ReactJS.
Continue reading “ReactJS Seed Application: Why Not Start with the Real Deal?”

@types · TypeScript Deep Dive

  • e.g. for jquery you should be able to just start using $ globally in your project.
  • @types supports both global and module type definitions.
  • npm install @types/jquery –save-dev
  • As can be seen having a definition that supports global leak in automatically can be a problem for some team so you can chose to explicitly only bring in the types that make sense using the tsconfig.json compilerOptions.types e.g.
  • By default any definitions that support global consumption are included automatically.

Definitely Typed is definitely one of TypeScript’s greatest strengths. The community has effectively gone ahead and documented the nature of nearly 90% of the top JavaScript projects out there.
Continue reading “@types · TypeScript Deep Dive”