Actor picture

Test JP


Test de JP

No credit card required

Author's avatarJavier Pinto
  • Modified
  • Users7
  • Runs449


root = true

indent_style = space
indent_size = 4
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true
end_of_line = lf


    "extends": "@apify"


# This file tells Git which files shouldn't be added to source control



# First, specify the base Docker image. You can read more about
# the available images at
# You can also use any other image from Docker Hub.
FROM apify/actor-node:16

# Second, copy just package.json and package-lock.json since it should be
# the only file that affects "npm install" in the next step, to speed up the build
COPY package*.json ./

# Install NPM packages, skip optional and development dependencies to
# keep the image small. Avoid logging too much and print the dependency
# tree for debugging
RUN npm --quiet set progress=false \
 && npm install --only=prod --no-optional \
 && echo "Installed NPM packages:" \
 && (npm list --only=prod --no-optional --all || true) \
 && echo "Node.js version:" \
 && node --version \
 && echo "NPM version:" \
 && npm --version

# Next, copy the remaining files and directories with the source code.
# Since we do this after NPM install, quick build will be really fast
# for most source file changes.
COPY . ./

# Optionally, specify how to launch the source code of your actor.
# By default, Apify's base Docker images define the CMD instruction
# that runs the Node.js source code using the command specified
# in the "scripts.start" section of the package.json file.
# In short, the instruction looks something like this:
# CMD npm start

# Empty project

This template is useful when you're already familiar with the Apify SDK and want to start
with a clean slate. It does not include `puppeteer` or `playwright` so install them manually
and update the Dockerfile if you need them.

If you're looking for examples or want to learn more visit:

- [Tutorial](
- [Documentation](
- [Examples](

## Documentation reference

- [Apify SDK](
- [Apify Actor documentation](
- [Apify CLI](

## Writing a README

See our tutorial on [writing READMEs for your actors]( if you need more inspiration.

### Table of contents

If your README requires a table of contents, use the template below and make sure to keep the `<!-- toc start -->` and `<!-- toc end -->` markers.

<!-- toc start -->
- Introduction
- Use Cases
  - Case 1
  - Case 2
- Input
- Output
- Miscellaneous
 <!-- toc end -->


    "title": "Input schema for the apify_project actor.",
    "type": "object",
    "schemaVersion": 1,
    "properties": {
        "test": {
            "title": "Test",
            "type": "string",
            "description": "There is testing input field description.",
            "editor": "textfield"
    "required": []


    "env": { "npm_config_loglevel": "silent" }


// This is the main Node.js source code file of your actor.

// Import Apify SDK. For more information, see
const Apify = require('apify');

Apify.main(async () => {
    // Get input of the actor (here only for demonstration purposes).
    const input = await Apify.getInput();

     * Actor code


    "name": "project-empty",
    "version": "0.0.1",
    "description": "This is a boilerplate of an Apify actor.",
    "dependencies": {
        "apify": "^2.0.7"
    "devDependencies": {
        "@apify/eslint-config": "^0.1.3",
        "eslint": "^7.0.0"
    "scripts": {
        "start": "node main.js",
        "lint": "./node_modules/.bin/eslint ./src --ext .js,.jsx",
        "lint:fix": "./node_modules/.bin/eslint ./src --ext .js,.jsx --fix",
        "test": "echo \"Error: oops, the actor has no tests yet, sad!\" && exit 1"
    "author": "It's not you it's me",
    "license": "ISC"