fix: update setup checklists with latest js package version

[ShubhamPalriwala]

What does this PR do?

Update js package version to 1.1.4 from 1.1.2

Type of change

• This change is a documentation update

Checklist

Required

• Filled out the "How to test" section in this PR
• Read How we Code at Formbricks
• Self-reviewed my own code
• Commented on my code in hard-to-understand bits
• Ran pnpm build
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues
• First PR at Formbricks? Please sign the CLA! Without it we wont be able to merge it 🙏

Appreciated

• If a UI change was made: Added a screen recording or screenshots to this PR
• Updated the Formbricks Docs if changes were necessary

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

Name	Status	Preview	Updated (UTC)
formbricks-cloud	⬜️ Ignored (Inspect)		Nov 7, 2023 8:24am
formbricks-com	⬜️ Ignored (Inspect)		Nov 7, 2023 8:24am

[github-actions]

Thank you for following the naming conventions for pull request titles! 🙏

[review-agent-prime]

apps/formbricks-com/app/docs/getting-started/framework-guides/page.mdx

It's good to see that you're updating the version of the Formbricks library. However, it's important to note that hardcoding the version number in multiple places can lead to inconsistencies and maintenance issues. Consider using a single source of truth for the version number, such as a configuration file or environment variable, and reference it in your code. This way, you only need to update the version number in one place.
Create Issue

    const formbricksVersion = "^1.1.4";
    var t = document.createElement("script");
    t.type = "text/javascript";
    t.async = !0;
    t.src = `https://unpkg.com/@formbricks/js@${formbricksVersion}/dist/index.umd.js`;

apps/formbricks-com/components/home/SetupTabs.tsx

Hardcoding sensitive information like environmentId and apiHost can pose a security risk and limit flexibility. Consider using environment variables or a secure configuration file to store this information. This not only improves security but also makes your code more flexible.
Create Issue

    const environmentId = process.env.FORMBRICKS_ENV_ID;
    const apiHost = process.env.FORMBRICKS_API_HOST;
    formbricks.init({
      environmentId: environmentId,
      apiHost: apiHost,
    });

[review-agent-prime]

Replace hardcoded version number with a variable reference to ensure consistency and ease of maintenance.

Suggested change

	!function(){var t=document.createElement("script");t.type="text/javascript",t.async=!0,t.src="https://unpkg.com/@formbricks/js@^1.1.4/dist/index.umd.js";var e=document.getElementsByTagName("script")[0];e.parentNode.insertBefore(t,e),setTimeout(function(){window.formbricks.init({environmentId: "<your-environment-id>", apiHost: "<api-host>"})},500)}();
	</script>
	<script type="text/javascript">
	!function(){var t=document.createElement("script");t.type="text/javascript",t.async=!0,t.src=`https://unpkg.com/@formbricks/js@${formbricksVersion}/dist/index.umd.js`;var e=document.getElementsByTagName("script")[0];e.parentNode.insertBefore(t,e),setTimeout(function(){window.formbricks.init({environmentId: "<your-environment-id>", apiHost: "<api-host>"})},500)}();
	</script>

[mattinannt]

thank you :-)
For patch updates this is not so important as the ^ in ^1.1.2 means that it automatically picks the highest path release when requesting the js file from the server.