jump to navigation

An Open Source Project I’m Very Interested In… May 8, 2019

Posted by kevinbe71 in Development, Javascript, node, TypeScript, Uncategorized, Web Development.
Tags: , , ,
add a comment

Deno, which, if all goes according to plan should hit the 1.0 mark at the end of the summer 2019, is a really cool project in the “Node” dev space.

“A secure JavaScript/TypeScript runtime built with V8, Rust, and Tokio”

A few of the most important issues in the “Javascript” development space are:
1. TypeScript always feels like an extra layer that requires more effort than it should.
2. Client and Server code, while mostly reusable, have some annoying differences (e.g. “global” vs “window”).
3. Security was an afterthought in Node.
4. Deep, deep, deep dependency graphs!
5. Offline development is more tricky than it should be.

Ryan Dahl aims to address these and a few other things with his second attempt at server-side Javascript. Deno is going to be pretty amazing if it delivers on what’s currently being promised. It does seem to be largely on track (or perhaps even ahead of schedule?) so 2019 is looking like a really great year in this space!

TypeScript Timeline October 13, 2018

Posted by kevinbe71 in Angular, Javascript, node, React, TypeScript, Uncategorized, Vue.
Tags: , , , , , , , , , , ,
add a comment

TypeScript is a very cleverly architected solution to adding types to Javascript. The team behind it managed to create something that still allows the flexibility of Javascript while remaining 100% compatible with it (Javascript files are TypeScript files to the compiling and there’s even the allowJs option if you’re too lazy to rename your pure javascript files to .ts).

One of the best decisions they made was to support structural typing instead of requiring a strict type match (like many static languages do, e.g. Java and C#).

That said, as I’ve read more news about key companies adopting TypeScript I’ve always wondered how this matched up with the actual release timeline. So, I went to the effort today to put that together. The screenshot below is a very low resolution image, so it is purely meant as a thumbnail (you can click on it to navigate to the screenshot I took):


TypeScript Release Timeline

However, if you’d like to interact with the timeline, you can use this URL: TypeScript Timeline

redux-api-middleware – iconv-loader warning August 15, 2016

Posted by kevinbe71 in Development, Javascript.
Tags: , , , , , ,
add a comment

I recently ran into an error using webpack with an electron based app I’m working on.  The error manifested from a webpack warning:

WARNING in [...base path removed...]~/encoding/lib/iconv-loader.js
Critical dependencies:
9:12-34 the request of a dependency is an expression
 @ [...base path removed...]~/encoding/lib/iconv-loader.js 9:12-34

How I ended up with this was:

  • I produced an isomorphic web app with react, redux and redux-api-middleware (using a gulpfile to bundle it because that’s what the yeoman template used).
  • I thought it would be great to share common code with an electron-based desktop app I was working on (using webpack because that’s what I’d chosen to use).
  • I combined code and ran into the error.

To help resolve the issue I explored a few web pages and found this one that solved the problem (thanks Jim Pick!): https://github.com/andris9/encoding/issues/16

I added the following to my webpack.config.js:

 plugins: [
   ... other plugins listed here ...,
   new webpack.NormalModuleReplacementPlugin(
       /\/iconv-loader$/, 'node-noop'
   )
 ]

 

Design a site like this with WordPress.com
Get started