Comments (7)
Add me to this list
from serverless.
@ac360 I'm definitely interested. I think site should be where all complied FE modules live so that the cli can have a simpler time of deploying the FE assets.
Have you thought much about how basic you want these modules to be? Are we talking a simple set of entry point files, are we talking a fully fledged build system?
from serverless.
@ac360 My first idea was to build an opinionated example with some of the battle tested tools like Gulp, JQuery, Moment, Lodash, JSPM, Mocha and so on... But after read your post, I thought about it and finally I agree with you. We have to keep it most simple as possible in order to the futur adopters don't have to learn an other tool than the tool which they are interested (JAWS + React in this case).
However, about extensibility, I reminds that React is a framework for View only, and is not supposed to be responsible for the calls to the backend. So, if we want build an example simple and clean too I think, we will need a structuration framework (Reflux for example or an other).
from serverless.
opening pandora's box with flux implementation @mbreton lol this is where the real debate starts,
@ac360 made a great comment on gitter chat "Currently, I think JAWS should support multiple front-end frameworks, and each should have their own repo within the JAWS organization"
utilizing various repo's via modules is the way to go under the jaws organization. I think for demo purposes simple hello with basic routes implemented, but if other maintiners want to add addional modules with implementation I think that is under consideration :), that way we have the freedom to implement any bleeding edge technologies modules with various implementations, add my vote +1
from serverless.
Just finished a poc react ssr jaws demo. ( acronyms dawg...)
Currently it is using api gateway tied to a lambda to render markup lambda side.
If you have react inspector installed you'll notice that the html
head
and body
elements are all actually react components rendered server side and bootstrapped on the client.
The build pipeline is explained in more detail over at jaws-stack/JAWS-cli/issues/9
Here is the live demo
Here is the source if anyone is looking for inspiration
It uses the same IAM and .env config as JAWS.
from serverless.
Update 8/13/15:
We’re currently working on a document that outlines the specifications for JAWS v1.0.0.
A proposed resolution to this issue in particular is included in that document.
Today or tomorrow, we will share the document for everyone to comment on because your feedback is essential.
from serverless.
Outdated
from serverless.
Related Issues (20)
- Installing plugins HOT 5
- Installing plugins ignores yarn and uses npm instead HOT 1
- Documentation links not working correctly HOT 2
- s3 event with existing: true combined with bucket resource definition causes serverless remove to fail due to race condition
- CLI options definitions were upgraded with "type" property (which could be one of "string", "boolean", "multiple")
- [V4] Typescript with ESM support HOT 7
- Bring back `aws-profile` CLI option in V4
- `Error: gzip: invalid header` blocking Framework usage HOT 1
- Serverless [email protected] InitializingFailed HOT 5
- Bitbucket Serverless Not deploying
- Code splitting with serverless build doesn't really work HOT 3
- Error: Internal Server Error at Authentication.getClientDataFromAccessKey HOT 4
- MFA is not working with sls offline HOT 4
- Failed to construct URL with https://ssm.${param:region}.amazonaws.com TypeError: Invalid URL HOT 4
- Feature Request: AWS DynamoDB Accelerator (DAX) Support in Serverless Framework
- Allow Serverless Dev to work with Apollo Server AWS_PROXY integration. HOT 1
- AWS Lambda Python 3.9 and above
- Local invoke tries to pull images that are no longer supported. Swap to pulling from aws images insteadof lambci.
- "EMFILE: too many open files" while running serverless deploy on Windows HOT 4
- Build override package Pattern V4 HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from serverless.