remult 0.27.18 → 0.27.19-next.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/esm/server/remult-api-server.js +1 -1
  2. package/esm/src/remult3/remult3.js +2 -22
  3. package/package.json +1 -1
  4. package/server/remult-api-server.js +3 -1
  5. package/src/remult3/remult3.js +2 -22
package/esm/server/remult-api-server.js CHANGED
@@ -335,7 +335,7 @@ export class RemultServerImplementation {
335
335
  await what(remult, myReq, myRes, genReq, origRes, req);
336
336
  }
337
337
  finally {
338
- // remultStatic.asyncContext.setInInitRequest(false)
338
+ remultStatic.asyncContext.setInInitRequest(false);
339
339
  }
340
340
  }
341
341
  });
package/esm/src/remult3/remult3.js CHANGED
@@ -19,24 +19,11 @@ export const flags = {
19
19
  };
20
20
  /*p1 - create-remult discussion
21
21
 
22
- p1 - should we add to remult some init code that populates remult based on a built in server route for current user.
23
- - yes, `remult.initUser` - the url will be /api/me
24
- - ask to add a todo example
22
+ p1 - ask to add a todo example
25
23
  - admin question
26
24
  - ask to add a user table + password hash
27
25
 
28
- - changeOrigin false to vite config
29
- - test angular with auth
30
- - check nextauth if the env variable should be called NEXTAUTH_SECRET or just AUTH_SECRET
31
- /** @type {import('next').NextConfig}
32
- const nextConfig = {
33
- experimental: {
34
- serverComponentsExternalPackages: ["knex"],
35
- },
36
- };
37
-
38
- export default nextConfig;
39
-
26
+
40
27
  p1 - Landing page:
41
28
  - p2 include the selections (react,vite, postgres,auth)
42
29
  - include server is alive test (remind to run dev-node)
@@ -48,13 +35,6 @@ export default nextConfig;
48
35
  - the selections
49
36
  - how to run dev
50
37
  - which environment variables to set
51
-
52
-
53
- - should we add admin? ensureSchema:false etc...
54
- - should we read existing database?
55
- - knex issue with next
56
-
57
-
58
38
  */
59
39
  //p1 - add aggregate to query
60
40
  //p1 - add parameter all to deleteMany, and updateMany
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "remult",
3
- "version": "0.27.18",
3
+ "version": "0.27.19-next.0",
4
4
  "description": "A CRUD framework for full-stack TypeScript",
5
5
  "homepage": "https://remult.dev",
6
6
  "repository": {
package/server/remult-api-server.js CHANGED
@@ -634,7 +634,9 @@ var RemultServerImplementation = /** @class */ (function () {
634
634
  case 7:
635
635
  _a.sent();
636
636
  return [3 /*break*/, 9];
637
- case 8: return [7 /*endfinally*/];
637
+ case 8:
638
+ remult_static_js_1.remultStatic.asyncContext.setInInitRequest(false);
639
+ return [7 /*endfinally*/];
638
640
  case 9: return [2 /*return*/];
639
641
  }
640
642
  });
package/src/remult3/remult3.js CHANGED
@@ -22,24 +22,11 @@ exports.flags = {
22
22
  };
23
23
  /*p1 - create-remult discussion
24
24
 
25
- p1 - should we add to remult some init code that populates remult based on a built in server route for current user.
26
- - yes, `remult.initUser` - the url will be /api/me
27
- - ask to add a todo example
25
+ p1 - ask to add a todo example
28
26
  - admin question
29
27
  - ask to add a user table + password hash
30
28
 
31
- - changeOrigin false to vite config
32
- - test angular with auth
33
- - check nextauth if the env variable should be called NEXTAUTH_SECRET or just AUTH_SECRET
34
- /** @type {import('next').NextConfig}
35
- const nextConfig = {
36
- experimental: {
37
- serverComponentsExternalPackages: ["knex"],
38
- },
39
- };
40
-
41
- export default nextConfig;
42
-
29
+
43
30
  p1 - Landing page:
44
31
  - p2 include the selections (react,vite, postgres,auth)
45
32
  - include server is alive test (remind to run dev-node)
@@ -51,13 +38,6 @@ export default nextConfig;
51
38
  - the selections
52
39
  - how to run dev
53
40
  - which environment variables to set
54
-
55
-
56
- - should we add admin? ensureSchema:false etc...
57
- - should we read existing database?
58
- - knex issue with next
59
-
60
-
61
41
  */
62
42
  //p1 - add aggregate to query
63
43
  //p1 - add parameter all to deleteMany, and updateMany