v6.2.2

What's Changed

• Improved Logging: Removed unnecessary logging from the CLI, streamlining the output for a cleaner user experience.
• React as Default: New themes are now created as React projects by default, simplifying the setup process for developers.

Full Changelog: v6.2.1...v6.2.2

6.2.2-beta.2

What's Changed

• Refactor code by @meetdhananifynd in #373

Full Changelog: v6.2.1...6.2.2-beta.2
Added section chunking for react theme.

v6.2.1

What's Changed

• Removed default fixed port 7071 and added dynamic port generation for enhanced security and flexibility during CLI login.
• Added handler that manages token expiration without triggering unnecessary Sentry alerts

New Contributors

• @jinalviranii made their first contribution in #354

Full Changelog: v6.2.0...v6.2.1

v6.2.0

What's Changed

Section Separation from Main Theme Bundle: In this release, we've enhanced the way sections are handled in the vue theme. Previously, all sections were added to the main theme bundle, causing a significant javascript blocking time, which impacted website performance. Now, sections are separated into their own chunks during the sync process. This optimisation removes the blocking time and improves overall performance metrics.

• Section chunking vue by @prashant-fynd in #364
  Full Changelog: v6.1.1...v6.2.0

v6.1.1

What's Changed

• Make Luxe default theme for react by @karanrainafynd in #363

Full Changelog: v6.1.0...v6.1.1

v6.1.0

What's Changed

• Support for Extension Sections by @karanrainafynd in #295
• Support for adding dynamic CDN in theme @prashant-fynd in #316
• Support for theme sync while serve is going on @ashokrdkr in #321
• Use CDN key complete from Grindor API by @ashokrdkr in #322
• Validate custom-page url's for special characters by @ashokrdkr in #327
• Fix login issue due to partners url replacement by @manishprajapati52 in #357

New Contributors

• @prashant-fynd made their first contribution in #316

Full Changelog: v6.0.0...v6.1.0

v6.0.0

What's Added

fdk version

• Added a new command to check the current version of your FDK.

fdk extension pull-env

• Added a command to retrieve extension context values (API Key, API Secret, and Launch URL) from the partners panel and update the current extension context.

fdk tunnel

• Introduced a command to start a local tunnel on a specific port, allowing public access to locally running applications.

What's Changed

fdk login

• Added support for changing the environment using the --host flag. You can specify the partner URL of your cluster.
  • Example: fdk login --host api.fynd.com
• Introduced a 2-minute server timeout. If the developer does not select an organization from the browser within 2 minutes, the server will automatically close.
• Enhanced error handling for port conflicts when the port is already in use.

fdk extension init

• Added a prompt to allow developers to choose between initializing an existing extension or creating a new one.
• Introduced the --template flag, enabling developers to specify the template they want to use (node-react, node-vue, java-react, or java-vue). The extension will be generated with the corresponding template’s boilerplate.

fdk extension preview

• Major enhancements to automate the process of starting the tunnel, updating the tunnel URL, and launching the frontend and backend processes in a single step. Developers need to add the fdk.ext.config.json file to their frontend and backend projects. Refer to the documentation for more details.

fdk extension launch-url

• Made the --api-key parameter optional. If not provided, the command will prompt the user to select an extension from the available options and use its API key.
• Made the --url parameter optional in the fdk extension launch-url set command. If not provided, the command will prompt the user to enter a URL.

What's Deprecated

fdk env

• The fdk env commands have been deprecated. To set the environment, please use the login command as described above.

fdk extension setup

• The fdk extension setup command has been deprecated. Users can now use the fdk extension init command to select and set up existing extensions.

Other Improvements

• Enhanced error messages to be more descriptive and user-friendly.

Full Changelog: v5.1.7...v6.0.0

v5.1.7

What's Changed

• Remove unnecessary logs while creating… by @ashokrdkr in #342
• Upgrade cheerio@1.0.0 by @Shivraj0 in #347
• Fixed cloudflare installation issue by @bhargavprajapatiFynd in #349

New Contributors

• @ashokrdkr made their first contribution in #342

Full Changelog: v5.1.6...v5.1.7

v5.1.6

What's Added

• Command Aliases Introduced:
  • ext as an alias for extension
  • preview as an alias for preview-url

What's Changed

• Enhanced Logging:
  • Improved logging for the following commands: extension preview-url, extension init, and the Cloudflare tunnel, resulting in a better user experience.
• Dependency Updates:
  • Upgraded most of the dependencies to their latest versions.
• Vue.js Upgrade:
  • Updated the Node + Vue.js extension boilerplate to use Vue 3, accessible via the extension init command.

What's Deprecated

• The Python + Vue.js and Python + React.js extension boilerplates have been deprecated and are no longer available in the extension init command.

Breaking Changes

• The minimum supported Node.js version has been raised to Node 16.

Full Changelog: v5.1.5...v5.1.6

v5.1.5

What's Changed

• Default tunnel cloudflared added for fdk extension preview-url.
• Ngrok tunnel can be also used with fdk extension preview-url --use-tunnel ngrok.
• To populate sample data inside development store fdk populate with additional development company listing added.
• Better error handling and user friendly command outputs
• fdk env ls command support deprecated

Full Changelog: v5.1.4...v5.1.5