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
What we're planning to do. Only includes minor and major releases, patch releases only fix errors, meaning they aren't planned, as our plan and hope is to write errorless code (which we'll never do, but we'll try our best to get as close as possible to that).
6
6
@@ -12,8 +12,46 @@ No plans made as of now. We'll be thinking about what could we do for a 3.4 rele
12
12
13
13
---
14
14
15
+
## 4.X plans
16
+
17
+
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.
18
+
19
+
-[ ] New features
20
+
-[ ]`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`.
21
+
-[ ]`release` support for Cargo.
22
+
-[ ] 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.
23
+
-[ ] 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).
26
+
-[ ] Runs pre-commit tasks _before_ staging, make them actually useful.
27
+
28
+
---
29
+
15
30
## 3.X
16
31
32
+
### Version 3.3 (Released)
33
+
34
+
-[X] Rewrite the `audit` feature.
35
+
-[X] Fix known issues.
36
+
-[x] Support it everywhere NodeJS
37
+
-[x] pnpm
38
+
-[x] yarn
39
+
40
+
### Version 3.2 (Released)
41
+
42
+
-[X] Enhancements
43
+
-[X] Add `launchCmd` to `fklaunch` for users to define how a project should start up.
44
+
-[X] Better `migrate` feature.
45
+
-[X] Respect exact versions from the previous lockfile.
46
+
-[X] Support `stats`' Recommended Community Standards across:
47
+
-[X] Deno
48
+
-[X] Cargo
49
+
50
+
### Version 3.1 (Released)
51
+
52
+
-[X] New features
53
+
-[X]`fuckingnode launch <project>` to immediately launch user's favorite IDE with the given project and update its dependencies.
54
+
17
55
### Version 3.0 (Released)
18
56
19
57
-[x] Make a proper logo for the project.
@@ -59,33 +97,16 @@ No plans made as of now. We'll be thinking about what could we do for a 3.4 rele
59
97
-[x] Prettifier
60
98
-[x] Updater
61
99
62
-
### Version 3.1 (Released)
63
-
64
-
-[X] New features
65
-
-[X]`fuckingnode launch <project>` to immediately launch user's favorite IDE with the given project and update its dependencies.
66
-
67
-
### Version 3.2 (Released)
68
-
69
-
-[X] Enhancements
70
-
-[X] Add `launchCmd` to `fklaunch` for users to define how a project should start up.
71
-
-[X] Better `migrate` feature.
72
-
-[X] Respect exact versions from the previous lockfile.
73
-
-[X] Support `stats`' Recommended Community Standards across:
74
-
-[X] Deno
75
-
-[X] Cargo
76
-
77
-
### Version 3.3 (Released)
78
-
79
-
-[X] Rewrite the `audit` feature.
80
-
-[X] Fix known issues.
81
-
-[x] Support it everywhere NodeJS
82
-
-[x] pnpm
83
-
-[x] yarn
84
-
85
100
---
86
101
87
102
## 2.X
88
103
104
+
### Version 2.2 (Released)
105
+
106
+
-[x] Per-project cleanup.
107
+
-[x] Flagless features via `fknode.yaml`.
108
+
-[x] Auto-flush for log files.
109
+
89
110
### Version 2.1 (Released)
90
111
91
112
-[x] Release the `audit` feature as an `npm` only experiment. Learn more [here](../learn/audit.md).
@@ -95,24 +116,3 @@ No plans made as of now. We'll be thinking about what could we do for a 3.4 rele
95
116
-[x] VSCodium
96
117
-[x] Atom (_it's unmaintained, but anyways..._)
97
118
-[x] Get this documentation finished.
98
-
99
-
### Version 2.2 (Released)
100
-
101
-
-[x] Per-project cleanup.
102
-
-[x] Flagless features via `fknode.yaml`.
103
-
-[x] Auto-flush for log files.
104
-
105
-
---
106
-
107
-
## 4.X plans
108
-
109
-
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.
110
-
111
-
-[ ] New features
112
-
-[ ]`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`.
113
-
-[ ]`release` support for Cargo.
114
-
-[ ] 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.
115
-
-[ ] Rebuild `commit`, so you tell it what files to commit and it:
0 commit comments