You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/about/roadmap.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,19 +8,20 @@ We'll expand (and rarely, but not impossibly, shrink) this roadmap as we make pr
8
8
9
9
This page also lists all minor and major releases since 2.X. Patches aren't listed, and most bugfixes aren't included (as we don't "plan" to fix bugs).
10
10
11
-
## Upcoming release
11
+
## Upcoming major release
12
12
13
-
These are very, VERY early plans; however since we do have ideas that imply breaking changes, we're already thinking about 4.0. Expect this list to drastically change and/or get removals.
13
+
These are early plans; however we're already working on 4.0[from this branch](https://github.com/FuckingNode/FuckingNode/tree/v4). Expect this list to change over time and/or get removals.
14
14
15
15
-[ ] New features
16
16
-[ ]`build`, to automate building. Especially useful in JavaScript. This would have a text-config file to define what tasks to run for building a project. It could be used in combination with `release`.
17
17
-[ ]`release` support for Cargo.
18
18
-[ ] Dual release support: using the `FnCPF` from the interop layer to allow publishing the same JavaScript package to both npm and jsr. This would be really helpful as jsr downloads do not always work well with npm projects.
19
19
-[ ] Rebuild `commit`, so you tell it what files to commit and it:
-[ ] Doesn't require you to stage files before (making it useless, as `git commit -a -m` is also just one command).
22
-
-[ ] Runs pre-commit tasks _before_ staging, make them actually useful.
23
-
-[ ] Allow for DIR-based running; in simpler terms, compute things like `fkn stats` to `fkn stats --self` or `fkadd` to `fkadd --self`, so the `--self` flag isn't necessary (except for commands like `fkclean` where it does make sense to have it).
20
+
-[x] Un-stages anything else to avoid committing randomly staged files.
21
+
-[x] Doesn't require you to stage the files _before_ (making it useless, as `git commit -a -m` is also just one command), and lets you stage files from the own command.
22
+
-[ ] Runs pre-commit tasks _before_ staging, making them actually useful.
23
+
-[X] Allow for DIR-based running; in simpler terms, compute things like `fkn stats` to `fkn stats --self` or `fkadd` to `fkadd --self`, so the `--self` flag isn't necessary (except for commands like `fkclean` where it does make sense to have it).
Copy file name to clipboardExpand all lines: docs/manual/audit.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Does your app use {x} feature? [V:XXX] [y/N]
32
32
33
33
The question prompted will vary on the identified "vulnerability vector" (denoted by the `[V:XXX]` code). Depending on your responses, we'll show different questions. Then we'll compute a percentage and show it to you, where 0% means _not worth fixing_ and 100% means _absolutely needs fixing_. This percentage, which we call Risk Factor, is computed using a basic scoring system and a bit of math.
34
34
35
-
We made a research paper-like page [here](../learn/audit.md) explaining in detail how this works.
35
+
We made [a research paper-like page here](../learn/audit.md) explaining in detail how this works.
0 commit comments