RazorLight
proposal-built-in-modules | RazorLight | |
---|---|---|
4 | 11 | |
891 | 1,482 | |
0.3% | - | |
0.0 | 0.0 | |
11 months ago | 7 months ago | |
HTML | C# | |
BSD 2-clause "Simplified" License | Apache License 2.0 |
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.
proposal-built-in-modules
-
Turboprop: JS Arrays as Property Accessors!?!
There is proposal for stdlib, but it will take some time until (if ever) it will reach stage 4.
-
Don't make me think, or why I switched to Rails from JavaScript SPAs
The working group most in charge of JS is ECMA's TC-39 (TC => Technical Committee) [0]. They've been taking a very deliberate, slow path to expanding the "standard" library because they take a very serious view of backwards compatibility on the web. Some proposals were shifted because of conflicts with ancient versions of things like MooTools still out in the wild, for instance. (This was the so-called "Smooshgate" incident [1].)
This may speed up a bit if the Built-In Modules proposal [2] passes, which would add a deliberate `import` URL for standard modules which would give a cleaner expansion point for new standard libraries over adding more global variables or further expanding the base prototypes (Object.prototype, Array.prototype, etc) in ways that increasingly likely have backwards compatibility issues.
TC-39 works all of their proposals in the open on Github [3] and it can be a fascinating process to watch if you are interested in the language's future direction.
[0] https://tc39.es/
[1] https://developers.google.com/web/updates/2018/03/smooshgate
[2] https://github.com/tc39/proposal-built-in-modules
[3] https://github.com/tc39/proposals
-
What NPM Should Do Today to Stop a New Colors Attack Tomorrow
There is a TC39 proposal for a "Javascript Standard Library." It's at stage 1, which is better than stage 0.
https://github.com/tc39/proposal-built-in-modules
-
[AskJS] What is the thing you hate the most about JS?
The standard library is a tough one. There is a proposal for built-in modules but it is very early days and miles away from what is needed. Clojure ships with functions that make the likes of Lodash and Ramda redundant. I think for a dynamic language an extensive library of functions for manipulating collections is essential. It is a real thing that once dynamic language codebases grow too big, they become a challenge to maintain. Therefore having functions that do a lot of common tasks for you mitigates that issue. Paired with immutability, lots of code just becomes data passing through pipelines, giving less surface area for bugs and making everything more concise and declarative.
RazorLight
-
Introducing TopazView: A Lightweight and Powerful View Engine
Yes, I have used Razor pages in non-website applications before where I needed to load the cshtml templates from a different source. I have written Line of Business apps (think WinForms or WPF) where the reporting spits out HTML with tables and charts. There are a number of similar projects to yours out there which I have used in the past such as RazorLight or RazorMachine.
- A Handlebar and Puppeteer Equivalent in C#?
-
Sending HTML based emails. Is there an easier way to dynamically generate the document?
Your mileage may vary but I've had good luck with the RazorLight library for generating HTML emails from a template with data merged in. Under the hood, it uses the ASP.NET Razor engine for applying a model to a template.
-
Email template engine
We use https://github.com/toddams/RazorLight in combination with serverless functions.
- Rendering HTML (C# windows forms) not working after deploy
-
Generating html in a hosted service
you could use a razor based engine to generate html based on a view model (your data). take a look at: https://github.com/toddams/RazorLight i use it to generate html emails
-
Don't make me think, or why I switched to Rails from JavaScript SPAs
Rails has a templating system for generating emails (standard HTML/ERB files). If you're running an ASP.NET Web API (not MVC) the best way of doing that I've found is via Razorlight which you have to set up manually - https://github.com/toddams/RazorLight
With Rails the standard is pretty much Devise or Omniauth (or both) - does everything for you. I've never found anything for ASP like Devise which gives you an entire login system with all the required views/migrations in a couple commands.
-
How would you setup a e-mail template / content in .NET in order to reference to templates when sending mail?
I use RazorLight: https://github.com/toddams/RazorLight
-
How to render a Razor view from a Console application?
Razor Light
- How do you manage transactional email templates?
What are some alternatives?
openapi-typescript-codegen - NodeJS library that generates Typescript or Javascript clients based on the OpenAPI specification
RazorEngine - Open source templating engine based on Microsoft's Razor parsing engine
proposal-pattern-matching - Pattern matching syntax for ECMAScript
scriban - A fast, powerful, safe and lightweight scripting language and engine for .NET
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
Handlebars.Net - A real .NET Handlebars engine
proposal-observable - Observables for ECMAScript
DotLiquid - .NET Port of Tobias Lütke's Liquid template language.
redwood - The App Framework for Startups
Mustache Sharp - An extension of the mustache text template engine for .NET.
proposal-record-tuple - ECMAScript proposal for the Record and Tuple value types. | Stage 2: it will change!
SmartFormat.NET - A lightweight text templating library written in C# which can be a drop-in replacement for string.Format