| import { writeFileSync } from 'fs'; | |
| import * as path from 'path'; | |
| import * as ts from 'typescript'; | |
| /** | |
| * Extracts files from tsconfig.json | |
| * | |
| * @param tsconfigPath | |
| * @returns | |
| */ |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <title>👨🏻🍳🅰️ Ngx Light by Younes @ Marmicode.io</title> | |
| <meta name="description" content="👨🏻🍳🅰️ Ngx Light" /> | |
| <meta name="viewport" content="width=device-width,initial-scale=1" /> | |
| <script type="importmap"> | |
| { | |
| "imports": { |
The ESM standard is considered stable in NodeJS and well supported by a lot of modern JavaScript tools.
ESLint does a good job validating and fixing ESM code (as long as you don't use top-level await, coming in ESLint v8). Make sure to enable the latest ECMA features in the ESLint config.
{
This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.
I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.
But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.
If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.
| @Component({ | |
| selector: 'wt-greeting', | |
| template: (ctx: WtGreeting) => ngHtml`<h1>Hello ${uppercase(ctx.name)}</h1>` | |
| }) | |
| class WtGreeting { | |
| @Input() name: string; | |
| } | |
| @Component({ |
Welcome to step by step hands-on guide to setup webpack in your upcoming typescript project. Please follow the steps and you should be able to create your own webpack project. Please download the source code from github.
You will learn below things:
webpack.config.js file and modify webpack.config.js based on our need.
https://github.com/PacktPublishing free to download books code by Packet
https://github.com/EbookFoundation/free-programming-books Very immense
| Horizontal layer | Examples | |
|---|---|---|
| Business logic | Application-specific logic, domain logic, validation rules | |
| Persistence | WebStorage, IndexedDB, File System Access API, HTTP, WebSocket, GraphQL, Firebase, Meteor | |
| Messaging | WebRTC, WebSocket, Push API, Server-Sent Events | |
| I/O | Web Bluetooth, WebUSB, NFC, camera, microphone, proximity sensor, ambient light sensor | |
| Presentation | DOM manipulation, event listeners, formatting | |
| User interaction | UI behaviour, form validation | |
| State management | Application state management, application-specific events |
| { | |
| "Afghan": "أفغاني", | |
| "Albanian": "ألباني", | |
| "Algerian": "جزائري", | |
| "American": "أمريكي", | |
| "Andorran": "أندوري", | |
| "Angolan": "أنغولي", | |
| "Antiguans": "انتيغوا", | |
| "Argentinean": "أرجنتيني", | |
| "Armenian": "أرميني", |
| #!/bin/bash | |
| # source: https://gist.github.com/francoisromain/58cabf43c2977e48ef0804848dee46c3 | |
| # and another script to delete the directories created by this script | |
| # project-delete.sh: https://gist.github.com/francoisromain/e28069c18ebe8f3244f8e4bf2af6b2cb | |
| # Call this file with `bash ./project-create.sh project-name` | |
| # - project-name is mandatory | |
| # This will creates 4 directories and a git `post-receive` hook. |