marionettejs / marionette-integrations Goto Github PK

I think we need to add simple progressive web app example with marionette.
How to run sw-precache in simple marionette app.

We need to make a release of this repo to make yo works for everyone.

I think we need travis here to run build all example which we have here. It will be easy to check if new changes don't break anything.
We already have travis.yaml but need to add

env:
  - secure:

to run travis-runner.sh

@samccone can you take care of this?

When running npm run build in the webpack2 module, eslint throws parsing errors:

/data/git/identity/ui-tests/webpack2/app/components/App.js
  1:1  error  Parsing error: The keyword 'import' is reserved

/data/git/identity/ui-tests/webpack2/app/components/ItemView.js
  1:1  error  Parsing error: The keyword 'import' is reserved

/data/git/identity/ui-tests/webpack2/app/initialize.js
  1:1  error  Parsing error: The keyword 'import' is reserved

This prevents the build from completing.

Grunt skeleton documentation refers to gulp.
a bad copy/paste I think ;)
https://github.com/marionettejs/marionette-integrations/tree/master/browserify-grunt

webpack-dev-server in Webpack is currently show app folder with sources.
Correctly add contentBase: "./public", into devServer section webpack.config.js to display Compiled app

We should add jspm

Hello. Yet one question about webpack integration.

How should we use stylus-loader?
There is nor plugin definition in webpack.config.js nor files with styl extension.

So may be this dependency unnecessary?

Steps to reproduce:

git clone [email protected]:marionettejs/marionette-integrations.git
cd marionette-integrations/browserify/
npm install
npm run build

My theory is that because backbone is only included as a dependency of backbone.marionette, require('backbone') only works when called from inside backbone.marionette

If I also npm install backbone the error goes away, but now you have 2 copies of backbone that might be different versions.

➜  browserify git:(master) npm ls
marionette-browserify@ /tmp/marionette-integrations/browserify
├── [email protected] extraneous
├─┬ [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]

in the webpack2 example in not installed the module backbone.radio, you need to install it and save in package.json, it will fix the error fired on npm start

npm install --save backbone.radio

Hello.

I try use integration with webpack. During build process I got next error:

ERROR in .//backbone.marionette/lib/backbone.marionette.js
Module not found: Error: Cannot resolve module 'backbone.radio' in C:\data\coding\mjs\node_modules\backbone.marionette\lib
@ .//backbone.marionette/lib/backbone.marionette.js 12:133-158

After some researching I found this line in webpack.config.js

 resolve: {
   modulesDirectories: [path.join(__dirname, './node_modules')],
   root: path.join(__dirname, './app')
  }

Webpack documentation says that

Just use a directory name, not a path. Use only if you expect to have a hierarchy within these folders

Then I deleted modulesDirectories property, and after this build the project with success

Webpack v1 is deprecated

It would seem that all of these webpack integrations no longer work. Is there a plan to help beginning Marionette users to get started using modern webpack installations?

Thank you.

It will be great to update all examples to v3 before if will be released.

hi,

in the webpack2 and probably webpack sub projects the package.json scripts include bash invocation of eslint and webpack, for example in the build script. however the project does not install them globally so as to bash have them s commands.

npm run lint && webpack -p as lint there resolves toeslint app invocation. however It does not work. I think this is due to I do not have eslint as a command on my shell. I try in the bash
$eslint and get command not found, same for the webpack.

when I npm install -g webpack, for exampe, I do not get the error for it as I have taken before, I think it will be same for the eslint, as well.

However, this seems to conflict with the behaviour that the webpack-dev-server --open can work even it is not available as a bash command, and I have not installed it globally only locally with npm install from inside the webpack2 dir.

Any insigths into this?

Not sure if issue or not.

The default webpack2 build serves the app from http://localhost:9000/public/index.html instead of http://localhost:9000/ like the other examples.

It's needed to add also Marionette with rollup

Here some frameworks which should be included

• Mocha
• Jasmine
• AVA (untill AVA will support browsers)
• Cypress
• CasperJS

Currently in the example integration, jQuery is loaded separate from the built javascript file and then used at a global level. Is this absolutely necessary? Or is there a way to use it more seamlessly with Browserify?

I've been thinking to add yeoman, so person can just generate simple skeleton which he/she needs and play with instead of cloning all repo with all skeletons.

Is it possible to add a starter kit with routing configured and some pages? I know that there is this guide
https://github.com/marionettejs/guides/blob/master/en/appendix/approuter/router.md,
But, it would be very appreciated, since this guide covers Marionette v2, Marionette already on v4 and these integrations are based on v3. Thanks.

Please add a Webpack TypeScript integration as well