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 }}
Repository navigation
chore(csv-import-export): scaffold the CSV import/export plugin package - #65
First of four stacked PRs for a CSV import/export plugin. This one is the package scaffold only: no business logic.
packages/csv-import-export/
├── package.json # private: true, ./strapi-admin + ./strapi-server exports
├── admin/ # tsconfigs from the @strapi/sdk-plugin 6.1.1 template, placeholder page
├── server/src/index.ts # empty lifecycle + registries
├── scripts/smoke.mjs # packs the tarball, loads the server build (CI runs it on Node 20)
├── eslint.config.mjs, vitest.config.mts
└── README.md, docs/index.md, LICENCE.md
This is the first package here with a React admin bundle, so it builds with strapi-plugin build instead of tsc.
The package is "private": true. release.yml publishes every non-private package whose version is not on npm yet, with or without a changeset, so merging an empty plugin would otherwise publish it. PR 4 removes the flag.
Stack: this PR → server → admin UI → demo, docs and release.
Evidence
Before: no package. After:pnpm lint && pnpm typecheck && pnpm test && pnpm build && pnpm package:check && pnpm docs:build all exit 0 at the root; strapi-plugin verify passes.
node scripts/smoke.mjs prints smoke ok: tarball has admin and server builds, server entry loads. With "files": ["README.md"] it fails with tarball is missing dist/admin/index.js, so it catches the packaging mistake that shipped admin-api 1.2.0 without its build.
Design, plans and verification record: fbritoferreira/documentation#36.
Merge Danger
Door: two-way
Blast Radius: none
Private package; nothing is published and no other package or the demo depends on it.
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@types/parse-path@7.1.0. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
First of four stacked PRs for a CSV import/export plugin. This one is the package scaffold only: no business logic.
This is the first package here with a React admin bundle, so it builds with
strapi-plugin buildinstead oftsc.The package is
"private": true.release.ymlpublishes every non-private package whose version is not on npm yet, with or without a changeset, so merging an empty plugin would otherwise publish it. PR 4 removes the flag.Stack: this PR → server → admin UI → demo, docs and release.
Evidence
After:
pnpm lint && pnpm typecheck && pnpm test && pnpm build && pnpm package:check && pnpm docs:buildall exit 0 at the root;strapi-plugin verifypasses.node scripts/smoke.mjsprintssmoke ok: tarball has admin and server builds, server entry loads. With"files": ["README.md"]it fails withtarball is missing dist/admin/index.js, so it catches the packaging mistake that shipped admin-api 1.2.0 without its build.Design, plans and verification record: fbritoferreira/documentation#36.
Merge Danger
Door: two-way
Blast Radius: none
Private package; nothing is published and no other package or the demo depends on it.