Gathering detailed insights and metrics for gulp-ps-tasks
Gathering detailed insights and metrics for gulp-ps-tasks
Gathering detailed insights and metrics for gulp-ps-tasks
Gathering detailed insights and metrics for gulp-ps-tasks
A collection of gulp tasks for PowerSchool plugin development.
npm install gulp-ps-tasks
Typescript
Module System
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
Apache-2.0 License
1 Stars
68 Commits
3 Watchers
2 Branches
3 Contributors
Updated on Jun 27, 2018
Latest Version
0.7.0
Package Id
gulp-ps-tasks@0.7.0
Unpacked Size
21.55 kB
Size
7.45 kB
File Count
4
NPM Version
6.1.0
Node Version
10.5.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
22
2
gulp-ps-tasks
is a collection of Gulp tasks that makes it easier and faster to develop PowerSchool customizations and deploy them to a PowerSchool "image" server (cdn).
npm install -g babel babel-cli babel-register babel-plugin-transform-es2015-modules-commonjs
npm install --save-dev gulp-ps-tasks
.babelrc
and local.gulpfile.babel.js
to the root of your project folder.local.gulpfile.babel.js
to gulpfile.babel.js
.A config.json
file is required for the following information:
config.json
file location can be specified one of three ways. As soon as a config file is found, the search for a config file stops and the first config file found is used. Note that the config path should only include the path to your config.json
file -- it should not include the config.json
filename itself. Trailing slashes don't matter, they will be removed if they're included.--config {configPath}
option to your gulp {taskname}
command. Example: gulp build --config /home/nathan/projects/plugins
.config.json
is placed in your project folder.PSTASKS_ROOT
, to the directory path of your config.json
file.If you have a large number of plugins, I recommend using method 3 because it allows you to create and maintain a single config.json
file that can be used across all of your plugins. However, if you want it to just work, use method 2.
The following config example should be used as a starting point for your own config.json
file.
{
"image_server_name": {
"sams_url": "https://sams.example.com",
"api_url": "https://api.example.com",
"deploy_credentials": {
"host": "sftp_host",
"user": "user",
"pass": "password",
"remotePath": "/path/to/assets/folder"
}
},
"image_server_name2": {
"sams_url": "https://sams.example.com",
"api_url": "https://api.example.com",
"deploy_credentials": {
"host": "sftp_host",
"user": "user",
"pass": "password",
"remotePath": "/path/to/assets/folder"
}
},
// Optional: If no --env options is passed to the deploy task,
// provide the "image_server_name" that should be used as a default
"default_deploy_target": "image_server_name"
}
In order to use the gulp tasks included here with your own project, make a copy of the local.gulpfile.babel.js
file and rename it to gulpfile.babel.js
.
Run a task using gulp {taskname}
build
Uses a preprocessor to insert the image server url into your project. Places the resulting files in the dist
folder.
package
Creates a .zip
file with using all of the files in the dist
folder. The build
task places its files in the dist
folder, so this task is almost always run after running build.
watch-deploy
Run the preprocessor
on everything in your project's src
folder and automatically deploy those files to your image server. Useful for making rapid development changes.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
75 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-14
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More