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
Many tests require network access to `api.metacpan.org` and will fail in isolated environments. This is expected behavior. The core functionality tests (like `t/moose.t`, `t/assets.t`, etc.) should pass.
117
+
118
+
## Asset Development
119
+
120
+
### Building Assets
121
+
122
+
```bash
123
+
# One-time build
124
+
npm run build
125
+
126
+
# Minified build (for production)
127
+
npm run build:min
128
+
129
+
# Watch for changes during development
130
+
npm run build:watch
131
+
```
132
+
133
+
### Asset Files
134
+
135
+
- Source files: `root/static/`
136
+
- Built files: `root/assets/`
137
+
- Build configuration: `build-assets.mjs`
138
+
139
+
## Code Quality
140
+
141
+
### Linting
142
+
143
+
The project uses `precious` to orchestrate various linters:
144
+
145
+
```bash
146
+
# Install precious (if not using Docker)
147
+
./bin/install-precious /usr/local/bin
148
+
149
+
# Lint all files
150
+
precious lint --all
151
+
152
+
# Lint specific files
153
+
precious lint path/to/file
154
+
155
+
# Auto-fix issues
156
+
precious tidy --all
157
+
```
158
+
159
+
### Git Hooks
160
+
161
+
Pre-commit hooks are configured to run `precious` automatically. Set them up with:
162
+
163
+
```bash
164
+
./git/setup.sh
165
+
```
166
+
167
+
## Docker Development
168
+
169
+
For a completely isolated environment, use Docker:
0 commit comments