cognite-create 0.2.18 → 0.2.21

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 (2) hide show
  1. package/package.json +1 -1
  2. package/templates/.cursor/rules/general.mdc +10 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cognite-create",
3
- "version": "0.2.18",
3
+ "version": "0.2.21",
4
4
  "description": "Create a Next.js app preconfigured with Cognite defaults.",
5
5
  "bin": {
6
6
  "cognite-create": "./bin/index.js"
package/templates/.cursor/rules/general.mdc CHANGED
@@ -8,7 +8,11 @@ Use the ShadCN MCP server to list the Cognite registry for components you can us
8
8
 
9
9
  Always use semantic Tailwind color classes (e.g., bg-primary, text-primary, border-primary) instead of arbitrary color values (e.g., bg-blue-600, text-red-500). This ensures consistency with the design system.
10
10
 
11
- Run `pnpm lint` after your changes to make sure you have fixed all potential errors.
11
+ All CogniteSDK calls should be done server side or in server components.
12
+
13
+ We can't use the cognite sdk in the browser as the COGNITE_CLIENT_SECRET is private.
14
+
15
+ Prefer server actions over API routes.
12
16
 
13
17
  When setting up auth rememeber to set up the oidcTokenProvider.
14
18
 
@@ -32,4 +36,8 @@ export const getToken = async (clientId: string, clientSecret: string) => {
32
36
 
33
37
  console.log("Token response:", data);
34
38
  return data.access_token;
35
- };
39
+ };
40
+
41
+ Always run `pnpm lint` after you make changes to make sure you have fixed all potential errors.
42
+
43
+ Make sure all client and server components are handled properly and you are not passing client events from server components.