proposal-do-expressions
proposal-import-assertions
proposal-do-expressions | proposal-import-assertions | |
---|---|---|
19 | 15 | |
1,066 | 390 | |
2.3% | - | |
0.0 | 0.0 | |
about 3 years ago | about 1 year ago | |
HTML | HTML | |
MIT 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-do-expressions
-
TypeScript Is Surprisingly OK for Compilers
> no pattern matching/switch expressions
They're still waiting on the do expression proposal for that (https://github.com/tc39/proposal-do-expressions), which has been in the bikeshedding stage for the past five years.
-
[AskJS] Opinions on using self executing functions as multi-line expressions.
At some point, it may be superseded by do blocks, but for now it's really your best bet.
-
What is this called? { id ? <Dashboard/> : <Login/> } and can I make it check for multiple things like a switch case?
But there is a proposal for do-expression : https://github.com/tc39/proposal-do-expressions
-
Using {Blocks} in Rust & Go for Fun & Profit
It's also the reason why do expressions are my most anticipated feature for JS.
-
Pipe Operator (|>) For JavaScript
> They should repurpose `do` so that `do {}` (without the `while`) is an expression that you can put statements inside and return the last statement.
There's a proposal for precisely that. Unfortunately, only Stage 1 though.
https://github.com/tc39/proposal-do-expressions
- Is a single ternary operator inside the returned JSX acceptable?
-
[AskJS] Is there ever a good use for loose blocks in JS?
It's one of the main reasons why I really want the do-expression propsal to work out, because then it would become:
- The TC39 Process
-
[AskJS] What are still present issues in contemporary (2022) JavaScript?
Do blocks. Okay, this is actually a proposal so maybe someday. Basically blocks that can resolve to an expression.
-
'The best thing we can do today to JavaScript is to retire it,' says JSON creator Douglas Crockford • DEVCLASS
Tomorrow, do expressions:
proposal-import-assertions
-
First use of Web-pack review: Restaurant page
SO, you're using webpack to support CSS imports here, BUT, did you know that you can do this in vanilla JS without webpack using something called import assertions:
-
Show HN: Deon.land – Deno.land?
This could be implemented as an import assertion[1]:
import foo from 'http://example.com/foo' assert { sha256sum: '...' }
This feature would even be useful in the web platform in general. Along with an assertion for importing plain text files (not just JSON files).
[1]: https://github.com/tc39/proposal-import-assertions
-
Updates from the 94th TC39 meeting
Worth noting that Import Assertions were downgraded to stage 2 from stage 3. The proposal page may continue to say "stage 3" until it can be updated.
Import Assertions: Proposal for syntax to import ES modules with assertions
-
Ideas For A Javascript Stricter Mode
Also, I'm not sure how that'd work with import assertions. That'd add another round of questions.
-
How to import text files like .css or .txt on Deno?
Hi, there is a way to import json file like:
-
You can import non-JS files into JavaScript without bundlers & loaders
If you want the real thing, you're looking for import assertions.
-
NPM changes image path??..
But it's still only a proposal, currently at stage 3 (which means it's almost finalised, pending any critical feedback or refinements, before it gets implemented). You can view the import assertions proposal on GitHub.
-
Import Assertion support on Safari?
I wouldn't use import assertions in any browser since they are still a stage 3 proposal so any browser which implements them is doing before it is standardized and shouldn't be relied upon for anything that matters.
-
Deno Joins TC39
There's an issue for that to be added as aprt of import assertions https://github.com/tc39/proposal-import-assertions/issues/11...
What are some alternatives?
native-messaging-bash - Bash Native Messaging host.
proposal-pattern-matching - Pattern matching syntax for ECMAScript
captureSystemAudio - Capture system audio ("What-U-Hear")
proposal-source-phase-imports - Proposal to enable importing modules at the source phase
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
WHATWG HTML Standard - HTML Standard
proposal-upsert - ECMAScript Proposal, specs, and reference implementation for Map.prototype.upsert
proposal-symbols-as-weakmap-keys - Permit Symbols as keys in WeakMaps, entries in WeakSets and WeakRefs, and registered in FinalizationRegistries
caya - a tiny useful simple language experiment
coffeescript - Unfancy JavaScript
proposal-async-context - Async Context for JavaScript