MSEdgeExplainers
angular-cli
MSEdgeExplainers | angular-cli | |
---|---|---|
18 | 91 | |
1,255 | 26,585 | |
1.1% | 0.0% | |
8.1 | 9.9 | |
4 days ago | 10 days ago | |
HTML | TypeScript | |
Creative Commons Attribution 4.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MSEdgeExplainers
- Microsoft Edge Side Panel API
-
Tether elements to each other with CSS anchor positioning
The spec is a W3C CSS working group draft: https://drafts.csswg.org/css-anchor-position-1/
It looks like less of a Chrome thing and more of an Edge thing? The Intent to Prototype [1] links to an Edge explainer [2] with Microsoft authors. It doesn't look like anyone has asked Mozilla for a position yet [3] but I expect if they get positive signals from web developers (us!) that will be soon.
[1] https://groups.google.com/a/chromium.org/g/blink-dev/c/vsPdd...
[2] https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/...
[3] https://github.com/mozilla/standards-positions/issues?q=anch...
- Make your design compatible with foldable device
-
HTML document subtitles?
Read the explainer here
- More than “Just a web app”
-
What's New In Microsoft Edge Devtools?
You can learn more about Focus Mode in this Edge explainer document.
-
Parcel CSS: A new CSS parser, compiler, and minifier
For a spec about a browser feature, "getting it" can mean a few different things.
1. Understanding the purpose of the feature ("why/when would I use this?")
2. Understanding how to implement the feature
3. Understanding how to use the feature
4. Understanding the feature's "corner cases" (surprising implications, cases where it doesn't do what you'd expect, etc.)
5. Understanding why the feature works the way it does (instead of some other way)
Most of the web specs really only explain how to implement a feature, and even then, they're not great at that, because they do such a poor job at explaining the purpose of the feature.
Assuming that you, like most of us, aren't working on implementing a browser, that means that web specs are mostly unhelpful to you. It's almost completely beyond the purpose of a spec to teach you how to use a feature, what its corner cases would be (which are often unknown at the time a spec was written), and why the specification says what it says.
This is an area where the web spec community has made some improvements in recent years. Nowadays, it's understood that new proposed specifications shouldn't just provide a specification, but also a separate "explainer" document, whose purpose is to communicate #1 (the purpose of the feature), and also persuade the other browser vendors to implement the feature. ("This will be really cool, and here's why…")
At a minimum, specs nowadays often include a non-normative "Motivation" section, as the CSS Nesting spec does. https://www.w3.org/TR/css-nesting-1/ I you'll find that you can "get" that spec much better than you can the CSS OM spec https://www.w3.org/TR/cssom-1/ which is old enough to buy alcohol and doesn't include a "Motivation" section.
You can often find explainer docs linked off of https://chromestatus.com/ e.g. https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/... I think you'll find that explainers are 10000% better for learning features than specs are. (They typically even discuss #3, #4, and #5, as they typically discuss alternative rejected approaches.)
-
Introducing transparent ads in Microsoft Edge Preview
Transparent ads are enabled through ad providers joining the Transparent Ads Provider program. More info on the program and the requirements for providers here - https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/TransparentAds/Program-Overview.md
-
The strangely difficult problem of drawing a box around text
Not necessarily for a Swift project, but your experience makes me wonder about the current web API for highlighting spans of text.
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/...
Complicated...
angular-cli
-
Initializing a Project with Any Git Repository - Code Recycle
module.exports = async (util, rule, host, injector) => { let list = await util.changeList([ { type: 'copy', source: 'git', from: { url: 'https://github.com/angular/angular-cli.git', match: '/packages/schematics/angular/directive/files', output: '/packages/schematics/angular/directive/files', }, pathTemplate: '@angular-devkit', contentTemplate: '@angular-devkit', pathTemplateSuffix: '.template', templateContext: { name: 'hello', standalone: true, selector: 'hello', 'if-flat': (input) => '' }, to: './hello-directive' }, ]); await util.updateChangeList(list); };
-
The State of Angular SSR Deployment in 2024
Well, scream though I have, the Angular team desperately needs to Remove NodeJS Dependencies, as it has already fallen behind from all frameworks concerning deployment. I'm still waiting for the response on this... 🦗 🦗 🦗 🦗
-
Master Angular 17.1 and 17.2
PR: feat(@angular-devkit/build-angular): add define build option to application builder
-
Replacing Angular Universal with SSR version 17.0
The new ssr CommonEngine source code
-
Trying to upgrade to angular 16. How to fix these errors ?
Source: https://github.com/angular/angular-cli/issues/25134
-
Issue after upgrading to Angular 15
I'm not sure how to solve this but here's something that looks similar to your issue - https://github.com/angular/angular-cli/issues/24373
-
Is anyone else experience sporadic sass failures after upgrading to Angular 15?
Sass errors after migrating from Angular 13 to 15 / Node 14 to 18
-
Angular 17 esbuild and base href
Edit: Found it at Github https://github.com/angular/angular-cli/issues/25574. So it seems to be a problem
-
Angular is Much Better, But is Angular Universal?
Remove Dependencies for NodeJs
-
Copilot for Docs
Is it possible to teach llm to read issues and answer questions such as how do I get angular 17 to output to dist instead of dist/browser with you can't do this with angular. However, in your CI CD pipeline, you can do a mv or robocopy or bla bla bla depending on context?
https://github.com/angular/angular-cli/issues/26028
It would be very useful because there are so many edge cases that aren't covered in the docs but are probably available in some kind of WON'T FIX issues.
What are some alternatives?
dropcss - An exceptionally fast, thorough and tiny unused-CSS cleaner
vscode-dev-containers - NOTE: Most of the contents of this repository have been migrated to the new devcontainers GitHub org (https://github.com/devcontainers). See https://github.com/devcontainers/template-starter and https://github.com/devcontainers/feature-starter for information on creating your own!
ngx-foldable - Angular library to help your build dual-screen experiences for foldable or dual-screen devices
ng-packagr - Compile and package Angular libraries in Angular Package Format (APF)
react-foldable - A set of components to help you work with foldable screens
BunkerWeb - 🛡️ Make your web services secure by default !
Tailwind CSS - A utility-first CSS framework for rapid UI development.
offline-plugin - Offline plugin (ServiceWorker, AppCache) for webpack (https://webpack.js.org/)
surface-duo-photo-gallery - This repo is an Angular re-implementation of the Surface Duo Photo Gallery sample
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
lightningcss - An extremely fast CSS parser, transformer, bundler, and minifier written in Rust.
brownie-angular-mix - Everything you need to use Angular with Brownie!