PhpStorm 2017.3 Help

Create New Project Dialog

File | New Project

Welcome Screen | Create New Project

Use this dialog box to create empty projects or generate framework-specific project stubs for developing applications.

The left-hand pane of the dialog box shows a list of project types for which stubs can be generated. The set of available project types depends on the installed and activated plugins. The contents of the right-hand pane depend on the selected project type. The field Location is common for all project types.

The project types are grouped under the PHP-Specific and Web categories. If you have any project templates saved, they are listed under the User Defined category.

On this page:

PHP empty project

The feature is supported only when the PHP plugin is installed and enabled.

The plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to get just a project folder without any contents. In the right-hand pane:

  1. In the Location text box, specify the path to the project folder where the project-related files will be stored.
  2. In the PHP Language Level drop-down list, specify the PHP functionality scope to get coding assistance for. Each functionality scope is associated with the PHP version that supports this functionality. Currently PHP 5.3, PHP 5.4, PHP 5.5, PHP 5.6, PHP 7, PHP 7.1, and PHP 7.2 levels are supported.

    No correlation between the PHP version used in the project and the language level is enforced. Although the language version of each interpreter is detected automatically, you can still tell PhpStorm to provide you with coding assistance that corresponds to another language level. However, if you attempt to use a code construct that is not supported by the specified language level, PhpStorm suggests a Switch to PHP <version> quick-fix.

  3. From the Interpreter drop-down list, choose the PHP interpreter to use in the current project by default. The list contains all the currently configured local and remote PHP interpreters. See Configuring Local PHP Interpreters and Configuring Remote PHP Interpreters for details.
  4. The Include path area shows a list of paths to PHP-related items below the PHP home directory. The specified include paths will be used:
    • By the require(), include(), fopen(), file(), readfile(), and file_get_contents() functions when looking for files to use.
    • By PhpStorm when resolving references to included files.

    Use the Add new.png  and Remove  delete.png buttons to manage the contents of the list. Use the Up arrowUp  and Down  arrowDown  buttons to change the order of items in the list.

PHP-specific project types

Project type Description
App Engine Project The feature is supported only when the Google App Engine for PHP plugin is installed and enabled.

The plugins are activated by default. If the plugins are disabled, enable them on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to get a project stub for developing applications that will run in the Google PHP Runtime Environment, see Google App Engine for PHP for details.

In the right-hand pane:

  1. In the Application ID text box, type the identifier of your application as you specified it on the Create application page.
  2. In the SDK directory text box, specify the path to the folder where the Google App Engine SDK for PHP is installed.
  3. In the Python executable text box, specify the location of the Python executable file. Type the path manually or click the Browse button browseButton and choose the executable file in the dialog box that opens.

Composer Project The feature is supported only when the Command Line Tools Support plugin is installed and enabled.

The plugins are activated by default. If the plugins are disabled, enable them on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to have a project stub created using the Composer template.

In the right-hand pane:

  1. In the Composer.phar area, appoint the composer.phar command definition file to use in project creation.
    • Use existing composer.phar: choose this option to use commands from a previously downloaded composer.phar and specify its location in the text box.
    • Download composer.phar from getcomposer.org choose this option to have a new instance of Composer downloaded. The composer.phar file will be saved under the project root folder specified in the Location text box.
  2. In the Package area, specify the package to install during the project creation.
    • Available packages: from this list box, select the package to install. Use the search field, if necessary: start typing the search string, as you type, the list dynamically reduces to show the packages that match the entered pattern.
    • Description: this read-only text box briefly explains the functionality of the selected package.
    • Version to install: from this drop-down list, select the package version. The contents of the list depend on the specific package.
  3. In the Settings area, specify advanced settings for generating a project stub and installing packages (dependencies):
    • Path to PHP executable: in this field, specify the location of the PHP engine installation folder.
    • Command line parameters: in this text box, type the additional command line parameters. For example, to have a package added to the require-dev section instead of the default require section, type --dev. For more information about Composer command line options during installation, see https://getcomposer.org/doc/03-cli.md.

Drupal Module The feature is supported only when the Drupal Support plugin is installed and enabled.

The plugins are activated by default. If the plugins are disabled, enable them on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to have a Drupal module created and set up.

In the right-hand pane:

  1. In the Drupal installation path text box, specify the root folder of the Drupal installation. Type the path manually or click the Browse button browseButton and select the relevant folder in the dialog box that opens.

Joomla! Integration The feature is supported only when the Joomla! Support plugin is installed and enabled.

The plugins are activated by default. If the plugins are disabled, enable them on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to get a project stub for developing an application using the Joomla! content management system.

In the right-hand pane:

  1. In the Joomla! installation path specify the folder where Joomla! is installed.
  2. From the Project Type drop-down list, choose the Joomla! unit type for the application you will develop in the project. According to this choice, PhpStorm will structure the stub and download the necessaey sources. The available options are:

WordPress Plugin The feature is supported only when the WordPress Support plugin is installed and enabled.

The plugins are activated by default. If the plugins are disabled, enable them on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to get a project stub for developing applications using WordPress, see WordPress for details.

In the right-hand pane: Type the project location and specify the folder where WordPress is installed. This folder should contain the wp-admin and wp-includes subdirectories.

Web

Project type Description
Angular CLI The feature is supported only when the NodeJS and AngularJS plugins are installed and enabled.

The NodeJS plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins. The AngularJS plugin is not bundled with PhpStorm, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.

Choose this option to get a stub where later you can automatically generate specific structures, such as Classes, Components, Routes, Pipes, Services, etc. using the Angular CLI command line interface.

In the right-hand pane:

  1. Specify the path to the folder where the project-related files will be stored.
  2. In the Node Interpreter field, specify the Node.js interpreter to use. Choose a configured interpreter from the drop-down list or choose Add to configure a new one, see Configuring Node.js Interpreters
  3. In the Angular CLI field, specify the path to the angular-cli package.

AngularJS The feature is supported only when the NodeJS and AngularJS plugins are installed and enabled.

The NodeJS plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins. The AngularJS plugin is not bundled with PhpStorm, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.

Choose this option to have the project structure set up and some sources generated based on the AngularJS framework template.

In the right-hand pane, specify the path to the folder where the project-related files will be stored.

Foundation The feature is supported only when the JavaScript Support plugin is installed and enabled.

The plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to have the project structure set up and some sources generated based on the Foundation framework template.

In the right-hand pane:

  1. Specify the path to the folder where the project-related files will be stored.
  2. From the Version drop-down list, choose the template version to use and click Create.

Dart The feature is supported only when the Dart plugin is installed and enabled.

The plugin is not bundled with PhpStorm, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.

Choose this option to have the project structure set up and some sources generated for a Dart application.

HTML5 Boilerplate The feature is supported only when the JavaScript Support plugin is installed and enabled.

The plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to have the project structure set up and some sources generated based on the HTML5 Boilerplate template.

In the right-hand pane:

  1. Specify the path to the folder where the project-related files will be stored.
  2. From the Version drop-down list, choose the template version to use and click Create.

Meteor App The feature is supported only when the Meteor plugin is installed and enabled.

The plugin is not bundled with PhpStorm, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.

Choose this option to have the project structure set up and some sources generated based on the Meteor frameworks.

In the right-hand pane:

  1. Specify the path to the folder where the project-related files will be stored.
  2. Specify the location of the Meteor executable file (see Installing Meteor).
  3. From the Template drop-down list, choose the sample to generate. To have a basic project structure generated, choose the Default option.
  4. In the Filename text box, type the name for the mutually related .js, .html, and .css files that will be generated. The text box is available only if the Default sample type is selected from the Template drop-dow list.

Node.js Express App The feature is supported only when the Node.js plugin is installed and enabled.

The plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to have the project structure set up and some project sources generated based on the Express framework.

In the right-hand pane:

  1. Specify the path to the folder where the project-related files will be stored.
  2. The path to the Node.js executable file node.exe and to the Node.js package manager file npm.cmd.
  3. The Express template engine to use. From the Template engine drop-down list, choose one of the following:
  4. The CSS engine to use. From the CSS engine drop-down list, choose one of the following:

PhoneGap/Cordova App The feature is supported only when the PhoneGap/Cordova plugin is installed and enabled.

The plugin is not bundled with PhpStorm, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.

Choose this option to have the project structure set up and some sources generated based on the PhoneGap, Apache Cordova, and Ionic frameworks.

In the right-hand pane:

  1. Specify the path to the folder where the project-related files will be stored.
  2. Specify the location of the executable file phonegap.cmd, or cordova.cmd, or ionic.cmd (see Installing PhoneGap/Cordova/Ionic).

React App The feature is supported only when the JavaScript Support plugin is installed and enabled.

The plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to generate a project using a globally installed create-react-app package, see React for details.

In the right-hand pane:

  1. Specify the path to the folder where the project-related files will be stored.
  2. In the Node Interpreter field, specify the Node.js interpreter to use. Choose a configured interpreter from the drop-down list or choose Add to configure a new one, see Configuring Node.js Interpreters
  3. In the create-react-app field, specify the path to the create-react-app package.
  4. Optionally, in the Scripts version field, specify a custom package to use instead of react-scripts during the project generation. This can be one of the packages forked from react-scripts, for example, react-awesome-scripts, custom-react-scripts, react-scripts-ts, etc.

React Native The feature is supported only when the JavaScript Support plugin is installed and enabled.

The plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to get a stub for developing a React Native application.

In the right-hand pane:

  1. Specify the path to the folder where the project-related files will be stored.
  2. In the Node Interpreter field, specify the Node.js interpreter to use. Choose a configured interpreter from the drop-down list or choose Add to configure a new one, see Configuring Node.js Interpreters
  3. In the React Native field, specify the path to the react-native-cli package.

Twitter Bootstrap The feature is supported only when the JavaScript Support plugin is installed and enabled.

The plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to create a project, set up its structure, and generate some sources based on the Twitter Bootstrap template.

In the right-hand pane:

  1. Specify the path to the folder where the project-related files will be stored.
  2. From the Version drop-down list, choose the template version to use and click Create.

Web Starter Kit The feature is supported only when the JavaScript Support plugin is installed and enabled.

The plugin is activated by default. If the plugin is disabled, enable it on the Plugins settings page as described in Enabling and Disabling Plugins.

Choose this option to create a project, set up its structure, and generate some sources in accordance with the Web Starter Kit requirements.

In the right-hand pane:

  1. Specify the path to the folder where the project-related files will be stored.
  2. From the Version drop-down list, choose the template version to use and click Create.

Yeoman The feature is supported only when the Yeoman plugin is installed and enabled.

The plugin is not bundled with PhpStorm, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.

Choose this option to get interface for generating framework-specific project stubs using the Yeoman tool.

The right-hand pane shows all the previously installed Yeoman generators. Select the required generator from the list, click Next, and proceed as described in Creating a Project Using Yeoman Generator.

User Defined

This list is displayed only if you have previously saved any project templates. Choose the relevant item based on its description, see Saving Projects as Templates for details.
Last modified: 6 December 2017

See Also