Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
All you need to start using the VTEX platform.
Important: The current master branch refers to the next
version. Make sure to use @next
when installing!
npm install -g vtex@next
VTEX Toolbelt is a command-line program that gives you access to all of the features in the VTEX platform.
With it you can:
master
, making it public in your account URL.The VTEX Toolbelt can be installed via npm. If you don't have it installed, you can get it bundled with node:
It's recommended that you install it globally (you may need sudo or administrative privileges):
npm install -g vtex@next
Now you can use the vtex
command:
$ vtex
Welcome to VTEX I/O
Login with vtex login <account>
Usage: vtex <command> [options]
Commands:
login Log into a VTEX account
logout Logout of the current VTEX account
list [query] List your installed VTEX apps
watch [log-level] Send the files to the registry and watch for changes
install <app> Install the specified app
uninstall <app> Uninstall the specified app
publish Publish this app
settings <app> [field] Get app settings
settings set <app> <field> <value> Set a value
settings unset <app> <field> Unset a value
workspace list List workspaces on this account
workspace create <name> Create a new workspace with this name
workspace delete <name> Delete this workspace
workspace use <name> Use a workspace to perform operations
workspace promote <name> Promote this workspace to master
setup eslint Setup a local eslint environment
Options:
-h, --help show help information
Start by using vtex login
to receive your credentials and be able to access other features.
Simply type this command and follow the instructions.
On an app directory, run vtex watch
and click on or copy the provided URL into your browser.
The vtex
command will now monitor your files for changes and sync them automatically.
You can use vtex login
to login with your VTEX ID credentials or vtex logout
if you're already logged in and want to change credentials.
When logging in, you will be asked for 3 things:
account
name of the store you wish to work one-mail
password
If you wish to work on another account
, logout and login again with that account
.
Note that watch
and publish
implicitly checks if you're logged, and if you're not, it asks your credentials before proceeding.
To develop an app locally, open the directory where your VTEX app is and then type:
vtex watch
Toolbelt will upload all your app files to the developer environment, print an URL for your use and watch for any changes you make to the files, which will be automatically synchronized.
Create a .vtexignore
file containing, on each line, paths you wish to ignore.
If no .vtexignore
is found, your .gitignore file is used instead.
To publish your VTEX app to VTEX App Store, use the vtex publish
command. The app will be published under the vendor name.
MIT
FAQs
The platform for e-commerce apps
The npm package vtex receives a total of 1,696 weekly downloads. As such, vtex popularity was classified as popular.
We found that vtex demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.