Sencha is in an extremely exciting period as we strive to make massive improvements to our products in order to better serve the needs of our community. Among several ongoing product initiatives and enhancements, improving the product trial experience and meeting developers on the channels they prefer and use has been a priority.
Sencha trials for our products (Ext JS, ExtReact, ExtAngular, ExtWebComponents) are now publicly available on public npm. Begin quickly and easily creating engaging applications with the package platform you are most familiar with.
Do you prefer Ext JS trials in zip format? We haven’t altered that experience; in fact, the page has a new look! Download and test the Best Javascript Framework in zip format for a 30-day free trial!
Here are the 3 quick steps to get Ext JS via public NPM and create your first app.
- Install the latest Ext JS version
$ npm install -g @sencha/ext-gen
- Generate your first Ext JS app
$ ext-gen app -a
- Open and explore your new app
$ cd ./my-app $ npm start
Ext JS Quick Start NPM Guide 👉
The Ext JS trial also includes add-on premium components such as D3 Adapter, Pivot Grid, Calendar, Exporter and many other design tools and plugins. Use the ZIP trial form to get zip downloads of all these tools included as part of the trial experience.
Give Our Enhanced Product Trials a Spin!
- Are you actively developing in React or Angular? Enhance your apps with easy to use ExtReact or ExtAngular components. Get trial versions free for 30-days:
Try ExtReact on NPM Try ExtAngular on NPM
- Did you know that Sencha’s ExtWebComponents product offers 140+ UI components that are designed to work with the framework of choice or a framework-agnostic development methodology?
If you have any questions, leave us a comment here or get in touch.
What's your reaction?
0
0
Do you still need to use the private NPM repo to get an activated version? Or can you add the activation step to the version you get from the public repo?
The reason I ask is that one of the more annoying part of shifting to using the NPM tooling was configuring our build server to be able to get the private NPM packages.
Activation packages are the only thing that is necessary on the private registry for 7.2. The activator packages can only be available there because of how our activation system works.
This is great news. Using the private repository was a pain in the ass.
Next, please continue in this direction by clarifying what are — and make easily available — the latest GPL versions. Use and adoption of the GPL version by open-source project developers is the wedge you need to get ExtJS into companies for internal tooling.
See also this project on npm — the current owner seems to be be agreeable in passing it to you.
https://www.npmjs.com/package/extjs