Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add node-fs-temporary #155

Closed
wants to merge 1 commit into from
Closed

add node-fs-temporary #155

wants to merge 1 commit into from

Conversation

marijanp
Copy link

No description provided.

@thomashoneyman
Copy link
Member

Hi @marijanp — the registry no longer accepts pull requests to add repositories to the new-packages.json and bower-packages.json registry files. Instead, please see:

https://github.com/purescript/registry#publish-a-package

However, I see you are using a non-GitHub package location. The registry is explicitly designed to support this, but during the registry alpha we do not support any locations except for GitHub. That's because the PureScript compiler's publish subcommand and, by extension, the Pursuit packages website only accept packages from GitHub. We'll be lifting this restriction as soon as we can replace the purs publish process (there is an issue tracking this on the registry-dev repo).

In the meantime, you can do one of:

  • mirror your repository to GitHub, and register that location
  • wait to register your repository until non-GitHub packages are supported

@marijanp
Copy link
Author

@thomashoneyman my package requires a patched version of node-os because it's javascript syntax is deprecated. node-os also does not seem to be maintained anymore. Any suggestions on how to proceed?

I'm asking because creating the issue to add my package seems to require that it builds successfully.

@thomashoneyman
Copy link
Member

All packages must compile to be registered. But you can choose what compiler to use — for example, if your project works with PureScript 0.14.0 you can publish it with that version.

Or am I misunderstanding you?

@thomashoneyman
Copy link
Member

If the issue is that you are pointing to an unregistered dependency (your fork of node-os) then unfortunately your only option is to get that dependency updated and registered or to register your fork and point to that instead.

Packages in the registry can only depend on other packages in the registry.

Of course if you just need this for your application development then you can point at git links directly — your dependencies don’t all have to be registered

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants