fulls1z3 / azure-functions-typescript Goto Github PK

View Code? Open in Web Editor NEW

45.0 45.0 14.0 1.05 MB

Seed project for backend development on Azure Functions with TypeScript

License: MIT License

TypeScript 79.47% JavaScript 15.59% Shell 4.94%

api azure azure-functions npm-package rest typescript

azure-functions-typescript's People

Contributors

Stargazers

Watchers

Forkers

amrfarid140 ygnr cvillicanascio spacem zsoumya hanssens regaez toomone alex-min johngrandson ksh5022 natraj4392 rudravsony eandbsoftware

azure-functions-typescript's Issues

automatic detection of functions by webpack

I'm submitting a ... (check one with "x")

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request

Current behavior
As far as I understand, with the current Webpack configuration will need to be updated every time a new Function is created. It makes life difficult, especially when you are migrating an existing project to use this template.

Expected/desired behavior

Automatically detect functions under src directory and bundle them invidually.

This can be achieved by adding an extra helper method to get all the directories under src and create webpack entry object.

To make things smooth, I used Parllel Webpack to do the bundling in parallel.

I already have such setup working in my project and I would be more than happy to share the setup if you are intersted.

An in-range update of copy-webpack-plugin is breaking the build 🚨

The devDependency copy-webpack-plugin was updated from `4.5.2` to `4.5.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

copy-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: Your tests failed on CircleCI (Details).

Commits

The new version differs by 3 commits.

48bc708 chore(release): 4.5.3
5fa69db fix(processPattern): add glob directory context to contextDependencies (#290)
5474889 docs: context option is a string, not array (#269)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of rimraf is breaking the build 🚨

The devDependency rimraf was updated from `2.6.2` to `2.6.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rimraf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: Your CircleCI tests were canceled (Details).

Commits

The new version differs by 6 commits.

9442819 2.6.3
42fe369 autopublish scripts
21fd3df bin test
8f1d3a1 update tap and glob for security stuff
f0bc3a1 update tap, add package-lock
692022b travis node version updates

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Unable to run build due to Typescript errors in a yarn workspace

I'm submitting a ...

[ ] Regression
[ ] Bug report 
[X] Support request
[ ] Feature request
[ ] Documentation issue or request

Current behavior
I ran npm run build and I got TS related errors.

ERROR in [at-loader] ../../node_modules/@babel/parser/typings/babel-parser.d.ts:11:70 
    TS1144: '{' or ';' expected.

ERROR in [at-loader] ../../node_modules/@babel/parser/typings/babel-parser.d.ts:16:80 
    TS1144: '{' or ';' expected.

ERROR in [at-loader] ../../node_modules/@babel/parser/typings/babel-parser.d.ts:11:64 
    TS2304: Cannot find name 'import'.

ERROR in [at-loader] ../../node_modules/@babel/parser/typings/babel-parser.d.ts:11:87 
    TS2339: Property 'File' does not exist on type '"@babel/types"'.

ERROR in [at-loader] ../../node_modules/@babel/parser/typings/babel-parser.d.ts:16:74 
    TS2304: Cannot find name 'import'.

ERROR in [at-loader] ../../node_modules/@babel/parser/typings/babel-parser.d.ts:16:97 
    TS2339: Property 'Expression' does not exist on type '"@babel/types"'.

ERROR in [at-loader] ../../node_modules/@types/react-dom/node_modules/@types/react/index.d.ts:2820:14 
    TS2300: Duplicate identifier 'LibraryManagedAttributes'.

ERROR in [at-loader] ../../node_modules/@types/react-dom/node_modules/@types/react/index.d.ts:2833:13 
    TS2717: Subsequent property declarations must have the same type.  Property 'a' must be of type 'DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>', but here has type 'DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>'.

ERROR in [at-loader] ../../node_modules/@types/react-dom/node_modules/@types/react/index.d.ts:2834:13 
    TS2717: Subsequent property declarations must have the same type.  Property 'abbr' must be of type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>', but here has type 'DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>'.

...

Expected/desired behavior
Running npm run build and not having errors throwed.

Minimal reproduction of the problem with instructions

git clone https://github.com/azure-seed/azure-functions-typescript.git
yarn
npm run build

What is the motivation / use case for changing the behavior?
I want to build

Environment

Node version: 10.16.0
Platform: Linux

Others

The app is in a sub-folder (a yarn workspace) in a monorepo so my node_module is in the root folder.
Seems to work out of a yarn workspace

make use of Google's JS and Material2 style guides

I'm submitting a ... (check one with "x")

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request

Current behavior

Expected/desired behavior

public members without prefix & private members with underscore _ prefix
add JSDocs
add JSDoc params for private members, enums, typedefs, etc

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

For Tooling issues:

Node version: XX
Platform:

Others:

fulls1z3 / azure-functions-typescript Goto Github PK

azure-functions-typescript's People

Contributors

Stargazers

Watchers

Forkers

azure-functions-typescript's Issues

automatic detection of functions by webpack

An in-range update of copy-webpack-plugin is breaking the build 🚨

The devDependency copy-webpack-plugin was updated from `4.5.2` to `4.5.3`.

An in-range update of rimraf is breaking the build 🚨

The devDependency rimraf was updated from `2.6.2` to `2.6.3`.

Unable to run build due to Typescript errors in a yarn workspace

make use of Google's JS and Material2 style guides

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

fulls1z3 / azure-functions-typescript Goto Github PK

azure-functions-typescript's People

Contributors

Stargazers

Watchers

Forkers

azure-functions-typescript's Issues

The devDependency copy-webpack-plugin was updated from 4.5.2 to 4.5.3.

The devDependency rimraf was updated from 2.6.2 to 2.6.3.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency copy-webpack-plugin was updated from `4.5.2` to `4.5.3`.

The devDependency rimraf was updated from `2.6.2` to `2.6.3`.