fixes files necessary to run and build

[fitzk]

fix typos, add .env.development file and update nodemon to run in --m…ode development explicitly

Summary by CodeRabbit

• New Features

  • Introduced a new environment configuration for development, enhancing local development setup.

• Security Enhancements

  • Updated content security policy to enforce HTTPS connections, improving the application's security.

• Configuration Updates

  • Modified build command to explicitly use development mode, optimizing the development process.

[coderabbitai]

Walkthrough

Walkthrough

The changes introduce a new .env.development configuration file for the mocksi-lite-next application, specifying the VITE_NEST_APP variable for local backend connectivity. The manifest.json updates enhance security by transitioning child-src and frame-src directives from http to https. Finally, the nodemon.json file's exec command is adjusted to set the build mode to development during the Vite build process.

Changes

Files	Change Summary
apps/mocksi-lite-next/.env.development	New file created with VITE_NEST_APP=http://localhost:3030.
apps/mocksi-lite-next/manifest.json	Updated child-src and frame-src from http to https; adjusted externally_connectable matches.
apps/mocksi-lite-next/nodemon.json	Changed exec command from "vite build" to "vite build --mode development".

Poem

In the garden, changes bloom,
With HTTPS, we chase the gloom.
A nod to dev with VITE's might,
Configs tidy, all feels right.
Hoppin' happy, we celebrate,
Code's a dance, let's elevate! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1e3f2db and 169e5f4.

Files selected for processing (3)

• apps/mocksi-lite-next/.env.development (1 hunks)
• apps/mocksi-lite-next/manifest.json (1 hunks)
• apps/mocksi-lite-next/nodemon.json (1 hunks)

Files skipped from review due to trivial changes (1)

• apps/mocksi-lite-next/.env.development

Additional comments not posted (2)

apps/mocksi-lite-next/nodemon.json (1)

5-5: Explicitly setting the build mode to development is appropriate.

The change to "exec": "vite build --mode development" ensures that the build process is explicitly set to development mode, which is beneficial for clarity and consistency during development.

apps/mocksi-lite-next/manifest.json (1)

18-22: Security enhancements by switching to HTTPS are commendable.

Updating the child-src, frame-src, and externally_connectable settings to use https improves the security posture of the application by enforcing secure connections.

[jonathankap]

👍