Code Monkey home page Code Monkey logo

silverstripe-module-starter's People

Contributors

colintucker avatar gordonbanderson avatar micschk avatar oilee80 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

silverstripe-module-starter's Issues

@silverstripe

Hi,
Btw: If you're writing SilverStripe admin module, you might want to add the @silverstripe module and implement its features in webpack.config.js

This makes it real easy to use SilverStripe components and other stuff in your React modules. Found out this week, working on my first SilverStrip Admin module try-out :-).

Martine

Build the repo for the new module

Hi,
Maybe document a few extra comments on how to build a brandnew repo for the newly created module? Because it basically still starts out as your repo :-)

Here's how I did it - might not be the best way, so please have a look, comments are welcome.

I started by creating an empty repo on Github

  1. adapted Licence and Readme
  2. uncommented node_modules and mapfiles in .gitignore
  3. removed setup.php and setup.json (and yarn.lock :))
  4. removed .git
  5. did a git init
  6. git remote add origin https://github.com/Martimiz/my-repo
  7. did the initial commit
  8. pushed to origin/master

If you agree I will gladly make a pulll

Martine

small config issues

Hi,
First of all many many thanks for setting up this supernice and much needed module!!!

I've run into a couple of small config issues that I'll address in one topic, if you don't mind :)

yarn

yarn.lock should probably be added to .gitignore I think

package.json:

running yarn install fails with:

The engine "node" is incompatible with this module. Expected version "^4.2.0".

That's because I'm using v8.6.0 and in package.json you have

"engines": {
"node": "^4.2.0"
},

Could that just be removed, you think?

webpack

running yarn build fails with:

[copy-webpack-plugin] WARNING - unable to locate 'mymodule/admin/client/src/images/icons'...

That directory isn't actually created, but referenced in webpack.config.js #127:

  if (src === PATHS.ADMIN.SRC) {
    common.push(
      new CopyWebpackPlugin([
        { from: path.resolve(src, 'images/icons'), to: 'images/icons' }
      ])
    );
  }

Should this be removed or should there be an actual icons folder. And is it supposed to contain icons?

Cheers, Martine

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.