Karl/Alexa-Couchpotato
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Alexa-Couchpotato/package.json

28 lines
835 B
JSON
Raw Permalink Normal View History

Couch Potato Alexa Skill 1.0
2016-03-27 14:35:30 -04:00
{
"name": "alexa-couchpotato",
Standardize searching for movies with optional release date (#17) * Don’t filter locally for year * Add new utterance for searching by year * Standardize release date query building * Update README with new utterances * Version bump to 1.1.1
2016-10-30 13:03:20 -04:00
"version": "1.1.1",
Couch Potato Alexa Skill 1.0
2016-03-27 14:35:30 -04:00
"description": "A skill to ask Alexa about your Couch Potato queue.",
Update the codebase to use ES6 and support Node v4.3 on Lambda (#13) Fixes #6 This required a few changes to the code base. First of all, we need to update our lambda function to use Node v4.3. This can be done in the Lambda console on AWS, and is also done in the default.env file. Next, since Node 4.3 doesn't offer full ES6 support yet, we need to run our source code through babel to transform it to be ES5-friendly. The ES6 source now lives in the src/ directory, and the transformed js is output into a dist/ directory. The dist/ package is what ends up getting uploaded to lambda. One last issue is that node-lambda doesn't work with ES6 either, so we need to make sure it runs against the files in the dist/ directory instead. You can use the test-lambda npm script to do this automatically for you by executing npm run test-lambda in the terminal. This will trigger running babel to transform the js and then running node-lambda against the newly transformed files in dist/.
2016-10-29 22:04:44 -04:00
"main": "src/index.js",
Couch Potato Alexa Skill 1.0
2016-03-27 14:35:30 -04:00
"scripts": {
Update the codebase to use ES6 and support Node v4.3 on Lambda (#13) Fixes #6 This required a few changes to the code base. First of all, we need to update our lambda function to use Node v4.3. This can be done in the Lambda console on AWS, and is also done in the default.env file. Next, since Node 4.3 doesn't offer full ES6 support yet, we need to run our source code through babel to transform it to be ES5-friendly. The ES6 source now lives in the src/ directory, and the transformed js is output into a dist/ directory. The dist/ package is what ends up getting uploaded to lambda. One last issue is that node-lambda doesn't work with ES6 either, so we need to make sure it runs against the files in the dist/ directory instead. You can use the test-lambda npm script to do this automatically for you by executing npm run test-lambda in the terminal. This will trigger running babel to transform the js and then running node-lambda against the newly transformed files in dist/.
2016-10-29 22:04:44 -04:00
"build": "babel src -d dist",
"zip": "cp -r {.env,deploy.env,package.json} dist/; cd dist; npm install --production; bestzip ../lambda.zip * .env;",
"bundle": "npm run build; npm run zip;",
"test-lambda": "npm run build; node-lambda run --handler dist/index.handler"
Couch Potato Alexa Skill 1.0
2016-03-27 14:35:30 -04:00
},
"author": "Joe Schmitt",
"license": "MIT",
"dependencies": {
"alexa-app": "^2.3.2",
"dotenv": "^2.0.0",
Move node-lambda to devDependencies
2016-03-27 16:25:09 -04:00
"node-couchpotato": "^0.1.4"
Couch Potato Alexa Skill 1.0
2016-03-27 14:35:30 -04:00
},
"devDependencies": {
Update the codebase to use ES6 and support Node v4.3 on Lambda (#13) Fixes #6 This required a few changes to the code base. First of all, we need to update our lambda function to use Node v4.3. This can be done in the Lambda console on AWS, and is also done in the default.env file. Next, since Node 4.3 doesn't offer full ES6 support yet, we need to run our source code through babel to transform it to be ES5-friendly. The ES6 source now lives in the src/ directory, and the transformed js is output into a dist/ directory. The dist/ package is what ends up getting uploaded to lambda. One last issue is that node-lambda doesn't work with ES6 either, so we need to make sure it runs against the files in the dist/ directory instead. You can use the test-lambda npm script to do this automatically for you by executing npm run test-lambda in the terminal. This will trigger running babel to transform the js and then running node-lambda against the newly transformed files in dist/.
2016-10-29 22:04:44 -04:00
"babel-cli": "^6.7.5",
"babel-core": "^6.7.6",
"babel-plugin-transform-runtime": "^6.7.5",
"babel-preset-es2015": "^6.6.0",
Couch Potato Alexa Skill 1.0
2016-03-27 14:35:30 -04:00
"bestzip": "^1.1.3",
Update the codebase to use ES6 and support Node v4.3 on Lambda (#13) Fixes #6 This required a few changes to the code base. First of all, we need to update our lambda function to use Node v4.3. This can be done in the Lambda console on AWS, and is also done in the default.env file. Next, since Node 4.3 doesn't offer full ES6 support yet, we need to run our source code through babel to transform it to be ES5-friendly. The ES6 source now lives in the src/ directory, and the transformed js is output into a dist/ directory. The dist/ package is what ends up getting uploaded to lambda. One last issue is that node-lambda doesn't work with ES6 either, so we need to make sure it runs against the files in the dist/ directory instead. You can use the test-lambda npm script to do this automatically for you by executing npm run test-lambda in the terminal. This will trigger running babel to transform the js and then running node-lambda against the newly transformed files in dist/.
2016-10-29 22:04:44 -04:00
"node-lambda": "^0.8.11"
Couch Potato Alexa Skill 1.0
2016-03-27 14:35:30 -04:00
}
}
Reference in New Issue Copy Permalink