Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.2K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 27 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 391 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
Getting below error when trying to run ojet serve command after installing Node js

Answers
-
The version of JET CLI does not match what you are using with your JET project. They must match starting with JET v12.
-
How to check the version of jet cli used in my project..I checked the ojet -- version in command line it was 12.0.0
-
The package.json in the project source directory contains a list of dependencies among which, the version of OJet is also listed
-
The core question remains however. How does one migrate from a previous version of OJet to the current?
Here is the migration section from the Developer Guide
--Rahul
-
The Migration chapter of the Developers Guide will help you with migration
You are correct in how you check the version of the CLI (ojet --version). Looking at the code of your project itself, you can look for the @oracle/oraclejet dependency line in the package.json file to get the major and minor release numbers. If there is a package-lock.json file in the project, I would recommend deleting that and letting it be regenerated with the new versions.
Depending on what version you are migrating from, you may have multiple dependencies in the path_mappings.json file that need to be updated as well, so don't miss that step in the Migration guide.