Home
About
Blog
Products
Forum
Support
Contact
Sunbelt Computer Software
PL/B Language Development and Support
Home
About
Blog
Products
Forum
Support
Contact
node-build-script/grunt.js at master · Preto/node-build-script · GitHub
Skip to content
Navigation Menu
Sign in
Appearance settings
Platform
AI CODE CREATION
GitHub Copilot
Write better code with AI
GitHub Copilot app
Direct agents from issue to merge
MCP Registry
Integrate external tools
DEVELOPER WORKFLOWS
Actions
Automate any workflow
Codespaces
Instant dev environments
Issues
Plan and track work
Code Review
Manage code changes
Code Quality
Enforce quality at merge
APPLICATION SECURITY
GitHub Advanced Security
Find and fix vulnerabilities
Code security
Secure your code as you build
Secret protection
Stop leaks before they start
EXPLORE
Why GitHub
Documentation
Blog
Changelog
Marketplace
View all features
Solutions
BY COMPANY SIZE
Enterprises
Small and medium teams
Startups
Nonprofits
BY USE CASE
App Modernization
DevSecOps
DevOps
CI/CD
View all use cases
BY INDUSTRY
Healthcare
Financial services
Manufacturing
Government
See all industries
View all solutions
Resources
EXPLORE BY TOPIC
AI
Software Development
DevOps
Security
View all topics
EXPLORE BY TYPE
Customer stories
Events & webinars
Ebooks & reports
Business insights
GitHub Skills
SUPPORT & SERVICES
Documentation
Customer support
Community forum
Trust center
Partners
View all resources
Open Source
COMMUNITY
GitHub Sponsors
Fund open source developers
PROGRAMS
Security Lab
Maintainer Community
GitHub Stars
Archive Program
REPOSITORIES
Topics
Trending
Collections
Enterprise
ENTERPRISE SOLUTIONS
Enterprise platform
AI-powered developer platform
AVAILABLE ADD-ONS
GitHub Advanced Security
Enterprise-grade security features
Copilot for Business
Enterprise-grade AI features
Premium Support
Enterprise-grade 24/7 support
Pricing
Search
/
Sign in
Sign up
Appearance settings
You signed in with another tab or window.
Reload
to refresh your session.
You signed out in another tab or window.
Reload
to refresh your session.
You switched accounts on another tab or window.
Reload
to refresh your session.
Dismiss alert
{{ message }}
Preto
node-build-script
Repository navigation
Code
Pull requests
Actions
Projects
Wiki
Security and quality
Insights
More
items
Files
Expand file tree
master
Breadcrumbs
node-build-script
/
grunt.js
Copy path
Blame
More file actions
Blame
More file actions
Latest commit
History
History
History
92 lines (85 loc) · 2.71 KB
master
Breadcrumbs
node-build-script
/
grunt.js
Copy path
Top
File metadata and controls
Code
Blame
92 lines (85 loc) · 2.71 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
//
// Our project gruntfile
// =====================
//
// Type grunt --help to see the support tasks, or browse the support/grunt-*.js
// files for further informations.
//
// Type grunt lint to run jshint through the sources.
//
// Type grunt test (or npm test) to run the default test suite (wrapper to Mocha)
//
// Type grunt test:<subtarget> to run the tests on a subset of files.
//
// Test
// ----
//
// Tests are stored in test/tasks/*.js. They run agains the files in test/h5bp
// which is a submodule pointing to h5bp/html5-boilerplate repository.
//
// test/helpers/* include utility functions to run grunt in a spawned process
// for a given task.
//
// test/features/*.feature are Gherkin feature file (cucumber) from which tests
// can be autogenerated. These are not unit tests, and may be seen more as
// functional tests. test/features/steps/*.js may contain step definitions, and
// are used to bootstrap basic and shared codes / assertions throughout our
// test suite.
//
// test/fixtures/* includes files that gets either copied before running a test,
// or expected files that get compared to files when a task is complete.
// Usually, they're stored within a folder mapping the related task's name.
//
// Type open test/index.html to see the generated documentation from our tests,
// done using the really neat mocha documentation reporter.
//
// Unit tests for each helpers defined remains to be done.
//
module
.
exports
=
function
(
grunt
)
{
// Project configuration.
grunt
.
initConfig
(
{
lint
:
{
grunt
:
[
'grunt.js'
,
'tasks/*.js'
]
,
lib
:
[
'lib/plugins/*.js'
]
}
,
watch
:
{
files
:
'<config:lint.grunt>'
,
tasks
:
'lint:grunt'
}
,
jshint
:
{
options
:
{
es5
:
true
,
node
:
true
,
curly
:
false
,
eqeqeq
:
true
,
immed
:
true
,
latedef
:
false
,
newcap
:
true
,
noarg
:
true
,
sub
:
true
,
undef
:
true
,
boss
:
true
,
eqnull
:
true
}
}
,
test
:
{
// each task is tested individually, with basic files comparison with
// what is in test/fixtures/
tasks
:
[
'test/tasks/test-*.js'
]
,
// default task with default options
builds
:
[
'test/tasks/default.js'
,
'test/tasks/usemin.js'
]
// css: 'test/tasks/test-css.js'
// img: 'test/tasks/test-img.js'
// tar: 'test/tasks/test-tar.js'
// usemin: 'test/tasks/test-usemin.js'
// docs: 'test/tasks/test-docs.js'
// html: 'test/tasks/test-html.js'
// init: 'test/tasks/test-init.js'
}
}
)
;
// Default task.
grunt
.
registerTask
(
'default'
,
'lint'
)
;
// load support for tasks, not part of the plugin functionnality.
// This gruntfile is our dev gruntfile.
grunt
.
loadTasks
(
'./support/'
)
;
}
;
You can’t perform that action at this time.