The Troubles With JavaScript Modules

Posted by: K. Scott Allen, on 04 Oct 2016 | View original | Bookmarked: 0 time(s)

This post is one in a series of posts where I describe common problems developers face using ES2015 features of JavaScript. In this post we look at modules. The Syntax Pitfall The first pitfall developers hit when using modules is making assumptions about the syntax. I fell into this trap myself. import {Person, Animal} from "./lib" Curly braces in JavaScript appear everywhere. We use them to define block statements, object literals, and more recently, use them for destructuring. Once I learned...

Category: JavaScript | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 164 | Hits: 11

Similar Posts

  • Issue 50 - DotNetNuke 5 Admin Modules Access, Reset Logins, iPhone OWS more
  • A Lightweight Event Framework in JavaScript more
  • DotNetNuke 5.1.0 Released more
  • Client Rendering Views with Spark and ASP.NET MVC more
  • New Release: BGI SCORM LMS Portal v2.5.0 - New Certification Manager with WYSIWYG Certificate Designer - DotNetNuke Integrated more
  • Custom JSON Serialization in ASP.NET AJAX more
  • JSON Serializers in .NET - not there yet more
  • Using the ClientAPI to retrieve safe JS strings for Localization in Gallery more
  • Shadow Modules in DotNetNuke using SQL more
  • How to manage ASP.NET validation from Javascript with jQuery more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD