#Visual studio code debug gulp task mac os x#
#Visual studio code debug gulp task install#
#Visual studio code debug gulp task code#

#Visual studio code debug gulp task code#

src/gulpfile.js contains JavaScript code that defines a set of Gulp tasks and their implementation logic.

#Visual studio code debug gulp task install#

This file tells the Node package manager (NPM) which packages it needs to download and install for the pipeline to function.

src/package.json contains information about the Node packages required by the pipeline.

Physically, the client-side asset pipeline consists of two files in the Orchard Core solution folder: For those using Visual Studio Code you can use its terminal. The pipeline defines a set of Gulp tasks that can be executed by Gulp using either the command line or using the Task Runner Explorer tool window in Visual Studio 2022 or later. The client-side asset pipeline is powered by Gulp, a popular open-source task runner based on Node.js that can be used to automate a wide variety of tasks in a development workflow. Many of the built-in modules and themes in Orchard Core use this pipeline to process client-side assets, and you can enable your own extensions to use it as well. Default is 'localhost'.Orchard Core includes a processing pipeline for client-side assets (typically scripts and stylesheets) which is used to perform front-end development workflow tasks such as transpilation, minification and bundling of client-side assets in both core projects and extensions (i.e.

If JavaScript source maps are enabled, the generated code is expected in this directory. Use JavaScript source maps (if they exist). Environment variables passed to the program. Optional arguments passed to the runtime executable. Default is the runtime executable on the PATH. Workspace relative or absolute path to the runtime executable to be used. Workspace relative or absolute path to the working directory of the program being debugged. Command line arguments passed to the program. Automatically stop program after launch.

Workspace relative or absolute path to the program. Name of configuration appears in the launch configuration drop down menu. ONLY 'node' and 'mono' are supported, change 'type' to switch. Add new configurations or edit existing ones. The absence of the ES6 setting, in particular, will yield errors related to unrecognized reserved keywords from the ES6 language specification. In this project, it enables ES6 support and defines CommonJS as the module system being used. Introduced in version 0.5.0 of Visual Studio Code, a few of its responsibilities are to indicate the level of ECMAScript support and to define the JavaScript module system. I’m calling it out solely for the important role it plays in the editor. If you’re following along with my GitHub repository, this file already exists.

More specifically, there are 3 files with which we must become familiar. Now that we’ve addressed a few housekeeping items, how would one debug an ES6-enhanced Gulp file in Visual Studio Code? Truth be told, there is a little bit of configuration required before it will work. Finally, the Node.js and Gulp versions being used are 0.12.7 and 3.9.0, respectively. More information on the version differences is available here.

#Visual studio code debug gulp task mac os x#

If you’re using Mac OS X or Linux, version 0.7.0 provides the equivalent feature set. To demonstrate what was described above, see my GitHub repository here for a very simple example and, if you’re expecting feature parity while following along in this blog post, Visual Studio Code 0.7.10 was used on Windows. But what does it actually mean? In short, rename your gulpfile.js file to, install the Babel NPM module at the project level ( npm install -save-dev babel), and begin leveraging ES6+ language features in your Gulp tasks. This feature is vaguely stated in the release’s change log on GitHub. By the way, Babel is the de facto standard ES6+-to-ES5 transpiler. One of the lesser known features of Gulp is the Babel support introduced in version 3.9 of the CLI.