#glimmer.js

[npmjs]

Customer Convo: Dan Gebhardt, Cerebris

This piece is a part of our Customer Convos series. We’re sharing stories of how people use npm at work. Want to share your thoughts? Drop us a line.

Q: Hi! Can you state your name and what you do? 

A: Hi there! I’m Dan Gebhardt. I’m a co-founder of Cerebris, which is a small web application consulting firm I run with my brother Larry Gebhardt. We’re pretty heavily into open source — I'm on the core teams for Ember.js, Glimmer.js, the JSONAPI spec, and Orbit.js.

How’s your day going?

Whew, it’s a hot one today in New Hampshire! But things are going well. I’m putting some finishing touches on a docs site for Orbit, which feels good because it’s been so long in the making.

What is your history with npm?

Although I’ve been working on web apps for a very long time, I haven’t done much Node development. As a result, I’ve only become a regular npm user in the past few years as it’s gained traction for front-end development. During that time, I’ve been really pleased to see how quickly npm has matured. And not just the npm service, which seems to have scaled quite well, but also the CLI, which is getting both faster and more deterministic (yay lockfiles!). 

What problem did you have that npm Orgs helped you fix?

Tom Dale and I started developing Glimmer.js as a standalone component library separate from Ember in late 2016. Although Ember itself is architected very modularly, the core framework does not feel very modular in practice because of the way it is currently published and typically consumed. When building Glimmer.js we quite deliberately decided to package and publish it as modularly as possible from the start. We not only wanted to share as much as possible between Ember and Glimmer — we also wanted to make packages as useful as possible on their own.

We chose to publish all of the core Glimmer packages through the @glimmer Org. This means that “official” packages all get an authoritative scope that differentiates them from non-scoped community packages. Furthermore, developers can use different packages, such as the dependency injection library @glimmer/di, independent from the rest of Glimmer.

How’s the day-to-day experience of using Orgs?

There’s very little friction to working with Orgs. As the rest of the Ember core team has gotten involved in developing Glimmer, assignments and authorization have been simple and straightforward. As packages are published, core team members are automatically assigned rights, which reduces the overhead of creating and managing packages. 

The only extra thing to remember about scoped packages is that they are private by default. So it’s necessary to explicitly publish packages with public access using `npm publish --access=public`. This is not a problem though, since you only have to remember this on the initial publish (and it’s no doubt a good safety check).

How would you see the product improved or expanded in the future?

I like using the npm CLI to manage packages, teams, and assignments, but a more interactive dashboard would be nice. Have I mentioned Ember.js? ;)

Would you recommend that other groups or companies use Orgs?

Most definitely. I can recommend Orgs for multi-package open source projects, even if they only have one member, because of the clarity that scoped packages provide to a community. Once you have multiple developers working on a project, you also gain the benefits of permission management. And even though I’ve only used Orgs for open source packages, I can easily see wanting to use private Orgs as well to get the same benefits for proprietary code.

What’s your favorite npm feature/hack?

I’ve become a real fan of using lerna for multi-package “mono-repos.” Lerna nicely solves the problem of managing dependencies across several local packages. Instead of needing to `npm link` them all individually, lerna can link them all together with one “bootstrap” command. It’s also quite useful for publishing multiple packages at once.

What is the most important/interesting/relevant problem with the JavaScript package ecosystem right now? If you could magically solve it, how would you?

A few months ago I would have said lockfiles, but I’m grateful that yarn and npm 5 have jumped that hurdle already. 

Instead, I’ll give a rather boring answer: I think we need more rigorous conventions for defining the entry points to our packages. In this era of advanced build tooling and transpilers, the current conventions around defining `main`, `module`, and even `types` in `package.json` seem inadequate. Stronger conventions could identify distributions by language (e.g., TypeScript), language level (e.g., ES5), and module format (e.g., commonjs). This would allow for automatic discovery of the least lossy version of sources appropriate for any given application, and allow for the most optimized JavaScript to be shipped to browsers using tools like babel-preset-env.

Any cool npm stuff your company has done that you’d like to promote?

Nothing specific to npm tooling, just lots of exciting stuff happening in the @glimmer, @ember, and @orbit Orgs :)

[javascriptlastnews]

Glimmer.js Progress Report https://t.co/G0iipHrxTX http://pic.twitter.com/UoMFPXlG6R

— JavaScript Facts (@mentallion) October 12, 2017

[hackernewsrobot]

Glimmer.js: What’s the Deal with TypeScript?

https://medium.com/@tomdale/glimmer-js-whats-the-deal-with-typescript-f666d1a3aad0 Comments

[technteacher]

Show HN: A Live Chat UI Using Glimmer.js

Show HN: A Live Chat UI Using Glimmer.js 2 by rajasegarc | from Blogger https://ift.tt/2QJ5YUP

[michaelhaynes]

#LinkedIn #Keeley Lighter than Lightweight: How We Built the Same App Twice with Preact and Glimmer.js https://t.co/vefkrQOSHj https://t.co/HWfvnF6r8z

#LinkedIn #Keeley Lighter than Lightweight: How We Built the Same App Twice with Preact and Glimmer.js https://t.co/vefkrQOSHj pic.twitter.com/HWfvnF6r8z

— Michael Haynes (@_michaelhaynes) March 13, 2018

via Twitter https://twitter.com/_michaelhaynes March 12, 2018 at 08:34PM

[krishaamer]

Tweeted

“Glimmer.js: What’s the Deal with TypeScript?” by @tomdale https://t.co/rrBtFdxAUg

— Kris Haamer (@krishaamer) March 12, 2018

[t-baba]

Web Design Weekly #295

Headlines

Is this my interface or yours?

John Saito shares some thoughts around interface items that belong to you. A great piece that sure does get you thinking. (medium.com)

Rebuilding Slacks Website (slack.engineering)

Manage projects. Bill your clients. Stay profitable.

Meet Harpoon, the all-in-one financial success platform for freelancers, studios, and agencies. You decide how much money you want your business to make this year. Harpoon provides the tools you need to help achieve that goal. Try it free for 14 days! (harpoonapp.com)

Articles

The whole web at maximum FPS

Lin Clark nerds out about WebRender which is part of Firefox Quantum. (hacks.mozilla.org)

Myths of Progressive Web Apps

As a fairly new and evolving concept, PWAs may be defined and understood differently by different people. In this post, Peter O’Shaughnessy shares some common myths about PWAs. (medium.com)

Bootstrap 4’s New Reset

Nicholas Cerminara explores some cool features of Reboot and how you can start using it today. (scotch.io)

REST versus GraphQL

A technical look at REST versus GraphQL, comparing and contrasting the two API specifications. (blog.pusher.com)

Exploring Data with Serverless and Vue

Sarah Drasner runs us through making use of a Serverless function and using Vuex to create a cutting edge demo. (css-tricks.com)

Mindsets every designer and researcher should embrace (usejournal.com)

React, Inline Functions, and Performance (reacttraining.com)

Tools / Resources

Image Effects with CSS

Bennett Feely has put together a great selection of image effects that can be achieved with CSS. Great little resource for some inspiration. (bennettfeely.com)

User Feedback is Key to Creating Awesome Experiences

What are your users actually thinking? Learn how to build an effective user testing plan and get actionable insights fast with this free guide. (usertesting.com)

Next.js 4

The latest version of Next.js shipped, which features support for React 16 and introduces a major upgrade for the default styling engine styled-jsx with support for dynamic styles. (zeit.co)

Nova

A colour scheme for modern web development (trevordmiller.com)

Live Theming with CSS Variables (jonathan-harrell.com)

The Curious Case of Mobx State Tree (codeburst.io)

Glimmer.js Progress Report (emberjs.com)

Cypress is now public beta (cypress.io)

Vue.js Style Guide (vuejs.org)

Inspiration

Advice for New Developers and Interviewing at Google (syntax.fm)

A Lifetime of Nerdery (css-tricks.com)

Jobs

Senior Front End Developer at Shopify

At Shopify we have one of the largest front end architectures in the world, and our front end development team works on making our client-side scalable, approachable, and an exceptional experience for hundreds of thousands of shop owners across the world. (shopify.com)

Front-End Engineer at Cloudability

Cloudability is seeking an exceptional Senior Software Engineer to join our team. The ideal candidate will thrive in a modern web development environment using ReactJS, Redux, SASS and other libraries. (cloudability.com)

Need to find passionate developers or designers? Why not advertise in the next newsletter

Last but not least…

The Depression Thing (zachholman.com)

The post Web Design Weekly #295 appeared first on Web Design Weekly.

by Jake Bresnehan via Web Design Weekly http://ift.tt/2ysCUcp

[h3adeu]

参考まで。 "Glimmer.js: What’s the Deal with TypeScript?" https://t.co/CHNkOvkEvP

参考まで。 "Glimmer.js: What’s the Deal with TypeScript?" https://t.co/CHNkOvkEvP

— ua5aw98z (@ua5aw98z) April 13, 2017

April 13, 2017 at 09:51PM

[javascriptlastnews]

Glimmeroids - Asteroids implementation using Glimmer.js https://t.co/x2fBq7QcWP http://pic.twitter.com/WTiMi7yh59

— JavaScript Facts (@mentallion) April 30, 2017

[javascriptlastnews]

Glimmer.js: What’s the Deal with TypeScript? https://t.co/pdsixmLvJA http://pic.twitter.com/W4xUctR6Ne

— JavaScript Facts (@mentallion) April 11, 2017