zkochan / package-preview Goto Github PK

There is going to be an infinite loop because package-preview is run before tests

• add an option to skip execution of some scripts (--skip-prepublishOnly)
• fail package-preview if it is called again inside another package-preview

Instead of naming the folder .foo.preview, name it smth like __preview__/foo

I'm trying to use a Lerna repo with this. Sometimes when I run tests there are changes across multiple modules which means that my tests won't work unless I publish all dependent modules first. Any tips on getting this working or is this out of scope for this module?

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• fix(deps): update dependency fs-extra to v11 (fs-extra, @types/fs-extra)
• fix(deps): update dependency meow to v12
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update dependency tape to v5 (tape, @types/tape)
• chore(deps): update dependency tempy to v3
• chore(deps): update dependency ts-node to v10
• fix(deps): update dependency load-json-file to v7

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @types/node to v14.18.48
• chore(deps): update dependency @types/node to v18
• chore(deps): update dependency execa to v7
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency typescript to v5
• fix(deps): update dependency write-json-file to v5
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Some toolings fail execution of prepublish/prepublishOnly to forbid publish.

I'm trying to use preview to test a submodule, as per this article:
https://jaketrent.com/post/import-parts-node-packages-slash/

Should this be possible? Can't tell if its a limitation of preview-package or I'm not building the package properly.

For context, I'm trying to make a module in my package available by requiring its path, e.g.

Instead of: require('myApp').start()

I would like require('myApp/start')

But I'm getting the error Cannot find module 'myApp/start'

I think I've achieved this by adding a start.js file that invokes the start method as: module.exports = app.start() and I can execute it from command line via node src/start.

• Peer dependencies installation
• Finding down a dir w/o node modules

Go up in the directory tree until the first directory that does not have parents with package.json or node_modules. If there is a package.json or node_modules in the system root folder, then fail

Currently it seems to pass thru

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

The other flag might not be needed

Version 4.0.7 of @types/fs-extra was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@types/fs-extra is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The pre/post install scripts

Probably not. At least by default not. But there should be a way to support this. Maybe through a flag or a package-preview-specific lifecycle event.

If the package has a preinstall script, it makes sense to remove its node_modules before every creation of the preview

 ! Cannot convert undefined or null to object

Error: Exit code: 1
    at ChildProcess.proc.on (/Users/dave/code/nm-prune/node_modules/@pnpm/exec/lib/index.js:46:35)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

opts passed in are:

{ args: [ 'install', '--production' ],
  cwd: '/Users/dave/__package_previews__/nm-prune',
  env: { PREVIEW_IS_RUNNING: '/Users/dave/code/nm-prune' } }

now that v6 of pnpm is released as latest, i've found that my projects that use package-preview have been breaking upon installation of pnpm with errors like the following: https://github.com/travi/javascript-scaffolder/runs/2304674064?check_suite_focus=true#step:5:535

i found that the behavior of installing the latest pnpm is due to the dependency on @pnpm/self-installer and was able to use the PNPM_VERSION environment variaable mentioned in Configuring to pin pnpm to latest-5.

it would be great if package-preview were compatible with the version of pnpm installed by default. i also see that @pnpm/self-installer is deprecated and the repo is archived, so this update would likely require adjustment to use the modern approach.

Version 1.1.0 of @pnpm/exec was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@pnpm/exec is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Preset name not found within published preset config (monorepo:angularmaterial). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.