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.

Sign up for GitHub

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

Jump to bottom

Project Structure Expectations #1

Open
jakethedev opened this issue Oct 1, 2018 · 2 comments
Open

Project Structure Expectations #1

jakethedev opened this issue Oct 1, 2018 · 2 comments

Comments

@jakethedev
Copy link

Hey there, Hacktober is a great time to follow up on stuff like this I think :)

Given some work in a subproject I have called Dungeonary, it might make a great start to this. How should this module be formatted, standard CommonJS require/export with all functions exported from the index? Or some other way?

Cheers!
@jakethedev jakethedev changed the title Question on format Project Structure Expectations Oct 1, 2018
@drewry
Copy link
Member

drewry commented Oct 1, 2018

That sounds great, I think the way you suggested will work perfectly!

@jakethedev
Copy link
Author

Rad! Then the PR could be as simple as "npm i -D dungeonary", but I'd be happy to fork just the important bits over when I get the chance to tidy them up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@drewry @jakethedev