Add cirru-parser

[tiye]

Corresponded PR in https://github.com/purescript/registry/pull/147/files . First time to submit package here...

I got a some confusions:

1. in dependencies field, I listed the packages I used manually. however among them the packages used in tests are not listed. when I was in Node.js there are dependencies and devDependencies. is that okay I leave out the devDependencies part in this?
2. does it also mean I need to PR every time I bumped version since version is locked here, even though my package is still in early stage? I tried but it appears I can't run pulp publish without the depended package listed in package-sets, I Googled many times and didn't see a way of maintaining dependencies locally(given that my package still in early stage and will probably change).

[thomashoneyman]

in dependencies field, I listed the packages I used manually. however among them the packages used in tests are not listed. when I was in Node.js there are dependencies and devDependencies. is that okay I leave out the devDependencies part in this?

Yes, you should leave out dev dependencies and only include dependencies used in your source.

does it also mean I need to PR every time I bumped version since version is locked here, even though my package is still in early stage? I tried but it appears I can't run pulp publish without the depended package listed in package-sets, I Googled many times and didn't see a way of maintaining dependencies locally(given that my package still in early stage and will probably change).

Yes, the version is locked here. You can either PR each time you bump the version, or you can wait for us to pick up the change (we update versions every couple days and check for updates automatically).

You don't have to have your library and its dependencies in the package set in order to work on it. You can rely on your packages locally -- see the section of the Spago documentation about overriding the package set to a local package.

Note that pulp doesn't know anything about package sets; pulp publish is used to push your package documentation to Pursuit and it uses your local bower.json file to do so, but it's unrelated to package sets.

There's one last thing -- if you are failing to run pulp publish because you have a dependency listed in your bower.json (like cirru-parser) and Bower says it doesn't know about the package, then that means that you published the package after the Bower registry officially closed. In that case, just make sure to provide the full Git URL to Bower instead of just the package name. For example:

- "cirru-parser": "^1.0.0"
+ "cirru-parser": "https://github.com/jiyinyiyong/purescript-cirru-parser.git#^1.0.0"

[tiye]

thanks a lot.

- "cirru-parser": "^1.0.0"
+ "cirru-parser": "https://github.com/jiyinyiyong/purescript-cirru-parser.git#^1.0.0"

this looks a lot like what I saw in Nim packages 😄

[tiye]

it has been 3+ days, could you tag a new release?

[thomashoneyman]

psc-0.14.0-20210324